Backup restore source validation and safety fixes
Cluster 122868. Data as of
Nothing open on GitHub. Fix merged in #124066 on 26 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #124066. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where corrupt or invalid SQLite sources could silently overwrite healthy databases during restore operations. The work involves adding source validation and honest reporting of refused or erroring restores.
Open issues0
Open PRs0
Fixes on record
-
#124066 fix(backup): restore never replaces a healthy database with a corrupt or #-path source
files:
hermes_cli/backup.py,hermes_cli/backup_restore.py,tests/hermes_cli/test_restore_source_integrity.py
2 PRs closed without merging
From the close comments: done elsewhere 2
Closed issues · 1
- Closed#122868bug(backup): corrupt restore sources overwrite healthy SQLite databases and report success
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.50: 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
- #124066
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 26 Sep 2026