Stale runtime backup dirs not cleaned up after repair
Cluster 73109 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #74490 on 30 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #74490. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #74490. That is separate from the fix event. - Still open
- Nothing open on GitHub.
After a successful managed-runtime repair, leftover venv.stale.runtime-* directories are not removed, accumulating significant disk usage. These members address detecting and cleaning up those stale backups.
Open issues0
Open PRs0
Fixes on record
-
#74490 fix(cli): reclaim stale venv.stale.runtime-* backups after runtime repair (salvages #73590)
files:
contributors/emails/[redacted:email],hermes_cli/managed_uv.py,hermes_cli/update_cmd.py,tests/hermes_cli/test_managed_uv.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#73590 fix(cli): remove venv.stale.runtime marker after successful managed runtime repair · merged via another change →
#74490,#73109,#72860
Closed issues · 1
- Closed#73109Successful managed-runtime repair leaves venv.stale.runtime-* behind permanently (1.1 GB per repair)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- hermes cli
- Merged PRs
- #74490
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 30 Jul 2026