ZIP backup integrity fixes for partial/incomplete reads
Cluster 124564. Data as of
Nothing open on GitHub. Fix merged in #125030 on 27 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 #125030. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #125030. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address scenarios where an incomplete or erroneous read during backup could result in a truncated or otherwise incomplete ZIP file being published. The fixes aim to prevent bad partial ZIP members from replacing a previous valid backup.
Open issues0
Open PRs0
Fixes on record
-
#125030 fix(backup): never publish an incomplete automatic zip over the previous backup
files:
hermes_cli/backup.py,hermes_cli/claw.py,tests/hermes_cli/test_backup.py,tests/hermes_cli/test_backup_zip_serialization.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#124589 fix(backup): discard failed partial zip members · done elsewhere →
9a6417c,#125030
Closed issues · 1
- Closed#124564Full backup can publish a truncated but CRC-valid ZIP member after a read failure
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
- #125030
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 27 Sep 2026