ref(seer): Read project preferences only from Sentry DB, part 1#113835
Merged
ref(seer): Read project preferences only from Sentry DB, part 1#113835
Conversation
srest2021
commented
Apr 23, 2026
…nce delete The _resolve_project_preference mocks in these tests targeted a function that no longer exists, and the tests asserted on a removed `repos` kwarg to _call_autofix. Replace mocks with real SeerProjectRepository setup and assert on call_kwargs["preference"].repositories instead. Refs CW-1175
Contributor
Backend Test FailuresFailures on
|
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 3aa1cc4. Configure here.
JoshFerge
approved these changes
Apr 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Relates to CW-1175
First step in migrating project-preference reads off the Seer API. Flips the following read call sites to read from the Sentry DB and removes the
organizations:seer-project-settings-read-from-sentryflag from them. Writes still dual-write via the Seer API. Types tightened where possible.Modified callsites:
ProjectSeerPreferencesEndpoint.getget_project_preferences/bulk_get_project_preferenceshas_project_connected_reposand removed the Seer API cache (no longer needed for a local DB hit)bulk_read_preferenceswrapper and_resolve_project_preference; callers usebulk_read_preferences_from_sentry_db/read_preference_from_sentry_dbdirectly._call_autofixnow derives repos frompreference.repositoriesitself._get_eligible_projectsand context engineindex_reposconsume typedSeerProjectPreferenceobjects directly instead of dict round-trippingAffected tests updated to create real
SeerProjectRepositoryrows and project options instead of mocking the Seer API. Removed tests for now-unreachable Seer-API fallback paths. Most of this large PR is just updated tests :)