Fix cache invalidation for nested pyproject.toml files #12727
Merged
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.
Summary
This PR fixes an issue with cache invalidation where changing a nested pyproject.toml didn't invalidate the cache for those files.
The root cause of the issue was that the
Resolver
returned the wrong configuration when querying the settings by the directory because it only registers a route fordirectory/{files}
but a query by directory misses the trailing/
.Fixes #12721
Fixes #12264
Test Plan
Played throught the example in #12721