Nothing open on GitHub. Fix merged in #111358 on 15 Sep 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 #111358. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #111358. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a bug where a hard-killed sync-back operation leaves a temporary tar archive on disk that grows until the disk fills, preventing the agent from starting. The members address detection and cleanup of these stale temporary archives.
Open issues0
Open PRs0
Fixes on record
-
#111358 fix(file-sync): a hard-killed sync-back no longer leaks its temp tar until the disk fills (#110812, salvage #110817)
files:
tests/tools/test_file_sync_back.py,tools/environments/file_sync.py
1 PR closed without merging
From the close comments: closed without comment 1
- #110817 fix(file-sync): clean stale sync-back temporary archives · closed without comment
Closed issues · 1
- Closed#110812file_sync: a hard kill leaks the sync-back temp tar (full-tree, uncompressed) until the disk is full and the agent cannot start
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
- Merged PRs
- #111358
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 15 Sep 2026