Add background autoprune to remove stale cache entries #17211
+252
−2
Conversation
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
TrevorBurnham
force-pushed
the
feature/cache-autoprune
branch
from
4886508 to
5e540fe
Compare
TrevorBurnham
force-pushed
the
feature/cache-autoprune
branch
from
5e540fe to
817c830
Compare
This was referenced Dec 21, 2025
Member
|
Do I understand it correctly that this doesn't remove old unpacked wheels generally, just archives having no symlinks pointing to them? I do think that needs to lock, there can be multiple uv versions running on a system and it's generally safer to lock than to use time based approaches. |
konstin
added
the
enhancement
TrevorBurnham
force-pushed
the
feature/cache-autoprune
branch
from
817c830 to
e20251d
Compare
Author
|
@konstin That's a very good catch! I've updated this PR to take the safer approach of only removing archives that are unreferenced. |
Implements automatic cache cleanup that runs in the background during normal uv operations. This addresses issue astral-sh#5731 by preventing unbounded cache growth without requiring user intervention. The autoprune task: - Spawns as a fire-and-forget background task when the cache is initialized - Removes unreferenced archives older than 1 hour (grace period for in-flight ops) - Requires no exclusive lock since archives are immutable and uniquely identified; if there's no symlink referencing an archive, no process can be using it This intentionally does NOT remove outdated bucket versions (e.g., wheels-v4), as different uv versions may be running concurrently on the same system. This is particularly useful for long-running processes like MCP servers where the cache cannot be manually pruned while uv is in use.
TrevorBurnham
force-pushed
the
feature/cache-autoprune
branch
from
e20251d to
3ff71d5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #5731
Summary
This PR implements automatic cache cleanup that runs in the background during normal
uv operations. This addresses issue #5731 by preventing unbounded cache growth
without requiring user intervention.
The autoprune task:
if there's no symlink referencing an archive, no process can be using it
Test Plan
I've added unit tests for this feature. Having said that, I'm new to this project, so I'd appreciate any suggestions for testing more thoroughly.