fix(builder): invalidate stale Python resolver indexes - #61
Draft
JohnXu22786 wants to merge 2 commits into
Draft
JohnXu22786 wants to merge 2 commits into
JohnXu22786 wants to merge 2 commits into
Conversation
Bump the resolver metadata version so existing incremental indexes rerun import resolution after resolver candidate ordering changes.
Ensure existing indexes rerun Python import and call resolution after the absolute-import candidate search changes.
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.
What this PR does
Before this PR:
Existing indexes persisted resolver metadata version 4 even after the Python absolute-import candidate search changed, so incremental builds could skip unchanged files and retain stale import and call edges.
After this PR:
Bump the resolver metadata version to 5 and add incremental regressions for project-root precedence, nested src ancestor fallback, and dependent call-edge repair.
Type of change
Bug fix
Breaking changes (if any)
None.