Nothing open on GitHub. Fix merged in #121498 on 24 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 #121498. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #121498. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members concern how the import process behaves when a backup archive contains a corrupt or damaged member, including a bug report about a crash and data overwriting, and at least two differing fix approaches around when or whether to abort.
Open issues0
Open PRs0
Fixes on record
-
#121498 fix(import): refuse a damaged backup archive before anything is overwritten
files:
hermes_cli/backup.py,hermes_cli/main.py,tests/e2e/core/upgrade/test_update_userstate_import.py,tests/hermes_cli/test_backup.py,website/docs/reference/cli-commands.md
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#121263 fix(backup): continue import after corrupt member · superseded by another PR →
#121498,#121258
Closed issues · 1
- Closed#121258[Bug]: `hermes import` of an archive with one corrupt member crashes with a zlib.error traceback after overwriting part of the home
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
- #121498
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 24 Sep 2026