Repository navigation
Conversation
zanieb
marked this pull request as ready for review
September 1, 2026 14:43
|
Promoted to #21400. |
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.
Concurrent uv processes sharing a cache could each extract the same local wheel or a wheel built from a source distribution. Source builds were serialized, but their lock was released before extracting the result, and the extraction locks were enabled only on Windows.
Acquire the lock for the source-specific wheel cache entry on every platform before checking for an extracted wheel, and hold it through publication. For built wheels, this remains scoped to the source revision and build settings, allowing waiting processes to reuse the completed extraction. Keep the existing Windows lock names for shared-cache compatibility and use bounded wheel cache keys elsewhere.