docs(embed): document uvx cache growth and how to reclaim it (#2915) - #3118
Merged
Conversation
The uvx-launched daemon keeps a cached Python environment per Hindsight version it has run (~1.5 GB each), and nothing removes them. Document the stop / prune / restart recovery, including why the daemon has to be stopped first.
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
1 participant
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.
Closes #2915.
The
uvx-launched embedded daemon keeps a cached Python environment for every Hindsight version it has run (~1.5 GB each) and nothing retires them — one reporter accumulated 35 generations / 55.5 GiB.We're resolving this as a documentation fix rather than adding cleanup logic. Reasoning, from checking the behaviour directly:
uv tool run(uvx) holds an open handle on~/.cache/uv/.lockfor the entire life of the daemon, and the embedded daemon runs with--idle-timeout 0. Souv cache pruneinvoked from the integration while a daemon is up blocks and then fails — it can only work once the daemon is stopped, which is exactly the manual sequence now documented.uv cache pruneis also machine-wide: it evicts cached environments for every other uvx-run tool on the host, not just Hindsight's.So this adds a short "Reclaiming Disk Space" section to the daemon docs with the stop / prune / restart sequence and a note on why the daemon must be stopped first.
Docs source only (
hindsight-docs/docs/) plus the regeneratedskills/mirror — the release script syncs it intoversion-0.8/at the next patch cut.