GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — fix: Add project filter to apply_data_source and delete_data_source by mailtoboggavarapu-coder · Pull Request #6298 · feast-dev/feast

Conversation

@mailtoboggavarapu-coder

@mailtoboggavarapu-coder mailtoboggavarapu-coder commented Apr 20, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor

Problem

Two methods in the shared registry were matching data sources by name only, without filtering by project. In multi-project registries where different projects share the same data source name (e.g. the default "vals_to_add"), this caused:

  • apply_data_source: cross-project overwriting of data sources
  • delete_data_source: deleting data sources from the wrong project

Fixes #6206

Changes

  • apply_data_source: already fixed — adds and existing_data_source_proto.project == project check (mirrors the pattern used in apply_entity, apply_feature_service, apply_feature_view)
  • delete_data_source: now uses the same project-scoped filter for consistency
  • Fix Unicode mojibake in comments (em dashes were stored as double-encoded Latin-1 bytes)

Testing

Existing registry tests cover this path. No new test added as the filter follows the exact pattern of other apply_* / delete_* methods in the same class.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@mailtoboggavarapu-coder
mailtoboggavarapu-coder requested a review from a team as a code owner April 20, 2026 15:17
devin-ai-integration[bot]

This comment was marked as resolved.

Sign in to view

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mailtoboggavarapu-coder mailtoboggavarapu-coder changed the title fix: add project filter to apply_data_source in shared registry scenario fix: add project filter to apply_data_source and delete_data_source Apr 20, 2026
@mailtoboggavarapu-coder
mailtoboggavarapu-coder force-pushed the fix/apply-data-source-project-filter branch from 945576e to 9378ca8 Compare April 20, 2026 21:34
@mailtoboggavarapu-coder

mailtoboggavarapu-coder commented Apr 20, 2026

Copy link
Copy Markdown
Contributor Author

Hi @woop @felixwang9817 @tedhtchang — this PR fixes a cross-project data source overwrite bug in the shared registry (issue #6206), adds the same project-scoped guard to delete_data_source for consistency, and fixes Unicode mojibake in comments. All 5 CI checks including DCO are passing. Would appreciate a review and merge when you get a chance — thank you! 🙏

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mailtoboggavarapu-coder

mailtoboggavarapu-coder commented Apr 20, 2026

Copy link
Copy Markdown
Contributor Author

Thanks for the automated review, @devin-ai-integration!

  • Bug Proto file fixes #1 (delete_data_source missing project filter): Already resolved in a previous commit — lines 429-432 now check both name and project.
  • Bug Create CI #2 (Unicode mojibake): Fixed in the latest commit — corrected the triple-encoded em dash and right-arrow characters on lines 697, 703, and 744 back to their proper Unicode code points (— and →).
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

devin-ai-integration[bot]

This comment was marked as resolved.

Sign in to view

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mailtoboggavarapu-coder

mailtoboggavarapu-coder commented Apr 21, 2026

Copy link
Copy Markdown
Contributor Author

Thanks for the style follow-up, @devin-ai-integration!

Style fix applied in the latest commit: the multi-line if condition in apply_data_source has been re-indented to 16/12 spaces to match the rest of registry.py (same pattern used by apply_entity, delete_data_source, apply_feature_service, etc.).

if (
    existing_data_source_proto.name == data_source.name
    and existing_data_source_proto.project == project
):

This keeps the formatting consistent with the surrounding code per AGENTS.md.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mailtoboggavarapu-coder

mailtoboggavarapu-coder commented Apr 21, 2026

Copy link
Copy Markdown
Contributor Author

Hi team! 👋 Friendly ping — this PR has been updated and is now current with master. All Devin review comments have been addressed. Ready for a human review when you get a chance!

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mailtoboggavarapu-coder

mailtoboggavarapu-coder commented Apr 21, 2026

Copy link
Copy Markdown
Contributor Author

Hi team! 👋 Friendly ping — this PR is now up-to-date with master. All review comments addressed. Ready for a human review when you get a chance!

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@ntkathole ntkathole changed the title fix: add project filter to apply_data_source and delete_data_source fix: Add project filter to apply_data_source and delete_data_source Apr 22, 2026
@ntkathole

ntkathole commented Apr 22, 2026

Copy link
Copy Markdown
Member

@mailtoboggavarapu-coder please sign the commit and also possibly please add the tests

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mailtoboggavarapu-coder

mailtoboggavarapu-coder commented Apr 22, 2026

Copy link
Copy Markdown
Contributor Author

Hi team! Checking in on this fix for the apply_data_source missing project filter issue. The branch has been updated with the latest from master. Happy to address any review comments!

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mailtoboggavarapu-coder
fix: Add project filter to apply_data_source and delete_data_source
5b34cbb
Fixes two methods in the shared registry that were matching data sources
by name only, without filtering by project. In multi-project registries
where different projects share the same data source name (e.g. the
default "vals_to_add"), this caused:

- apply_data_source: cross-project overwriting of data sources
- delete_data_source: deleting data sources from the wrong project

Changes:
- apply_data_source: adds and existing_data_source_proto.project == project
  check (mirrors the pattern used in apply_entity, apply_feature_service,
  apply_feature_view)
- delete_data_source: uses the same project-scoped filter for consistency
- Fix Unicode mojibake in registry.py comments (em dashes and right arrows
  were stored as double-encoded Latin-1 bytes)
- apply ruff format - collapse single-line timestamp assignment

Fixes feast-dev#6206

Signed-off-by: Venkateswarlu Boggavarapu <[email protected]>
@mailtoboggavarapu-coder
mailtoboggavarapu-coder force-pushed the fix/apply-data-source-project-filter branch from df7fc5a to 5b34cbb Compare April 22, 2026 15:36
@mailtoboggavarapu-coder
test: add cross-project isolation tests for apply/delete_data_source
43faac7
Add two integration tests that verify the regression fix for feast-dev#6206:

- test_apply_data_source_cross_project_isolation: applies a FileSource
  with the same name to two separate projects and asserts that updating
  one project's source does not overwrite the other project's source.

- test_delete_data_source_project_scoped: applies a FileSource with the
  same name to two projects, deletes it from one, and asserts the other
  project's source is unaffected.

Signed-off-by: Venkateswarlu Boggavarapu <[email protected]>
@mailtoboggavarapu-coder

mailtoboggavarapu-coder commented Apr 22, 2026

Copy link
Copy Markdown
Contributor Author

Hi @ntkathole — thanks for the review feedback! I've addressed both points:

1. Signed commits (DCO): The branch has been squashed into a single signed commit with Signed-off-by: Venkateswarlu Boggavarapu <[email protected]>. All prior unsigned commits (style fixes, merge commits) have been removed from the history.

2. Tests: Added two integration tests to sdk/python/tests/integration/registration/test_universal_registry.py:

  • test_apply_data_source_cross_project_isolation — creates a FileSource with the same name in two projects, updates one, and asserts the other project's source is not overwritten (direct regression test for apply_data_source method matches by name only, without filtering by project in shared registry scenario #6206).
  • test_delete_data_source_project_scoped — creates a FileSource with the same name in two projects, deletes it from one, and asserts the other project's source is unaffected.

Both tests follow the existing all_fixtures parametrize pattern. Please let me know if you'd like any changes — happy to iterate!

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

mailtoboggavarapu-coder added 4 commits April 22, 2026 12:57
@mailtoboggavarapu-coder
style: apply ruff formatting fixes to registry.py
eb71758
Signed-off-by: Venkateswarlu Boggavarapu <[email protected]>
@mailtoboggavarapu-coder
style: fix ruff E302 missing blank line before test function
58e4a38
Add missing blank line between top-level test functions to satisfy ruff E302.

Signed-off-by: Venkateswarlu Boggavarapu <[email protected]>
@mailtoboggavarapu-coder
DCO Remediation Commit for 58e4a38
c438089
I, mailtoboggavarapu-coder <[email protected]>, hereby attest that 58e4a38 adheres to the Developer Certificate of Origin.

Signed-off-by: mailtoboggavarapu-coder <[email protected]>
@mailtoboggavarapu-coder
DCO Remediation Commit for eb71758
528aa8f
I, mailtoboggavarapu-coder <[email protected]>, hereby attest that eb71758 adheres to the Developer Certificate of Origin.

Signed-off-by: mailtoboggavarapu-coder <[email protected]>
@mailtoboggavarapu-coder

mailtoboggavarapu-coder commented Apr 22, 2026

Copy link
Copy Markdown
Contributor Author

The DCO check is failing for two commits (eb71758 and 58e4a38) that were made via the GitHub web editor. The issue is that GitHub used the account display name mailtoboggavarapu-coder as the git author name for those commits, but the Signed-off-by lines say Venkateswarlu Boggavarapu.

All four original commits have matching Signed-off-by — it's just a name mismatch between the account display name and the real name used in the sign-off.

I've added DCO Remediation Commits for both affected SHAs (commits c438089 and 528aa8f), but the DCO bot doesn't seem to be recognizing them. The core code changes are correct and all CI lint checks should pass.

If you're able to use Squash and merge, the merge commit can carry a single proper Signed-off-by. Alternatively, if you can guide me on a preferred way to resolve this (e.g., a git rebase locally), I'm happy to follow whatever process the project requires. Thank you!

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mailtoboggavarapu-coder
Merge branch 'master' into fix/apply-data-source-project-filter
163625a
@mailtoboggavarapu-coder

mailtoboggavarapu-coder commented Apr 22, 2026

Copy link
Copy Markdown
Contributor Author

Closing in favour of #6319 which has a clean DCO-compliant commit history. Both commits in #6319 are authored as "Venkateswarlu Boggavarapu" matching the Signed-off-by, so the DCO check will pass. All the same changes (registry.py fix + tests) are included.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mailtoboggavarapu-coder mailtoboggavarapu-coder closed this Apr 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@devin-ai-integration devin-ai-integration[bot] devin-ai-integration[bot] left review comments

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

apply_data_source method matches by name only, without filtering by project in shared registry scenario

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@mailtoboggavarapu-coder @ntkathole
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.