Cairn
NousResearch/hermes-agent

Snapshot restore falsely reports success on refusal

Cluster 95763 · hermes cli. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues address a bug where the snapshot restore command prints a success message even when the database restore is refused, particularly when holder scans are incomplete. The fixes prevent destructive restores in that scenario and correct the misleading output.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · stale or abandoned 1

  • #95764 fix(state): do not print success when snapshot DB restore is refused · done elsewhere → 1f7cb4f, e907a9a, 44248a0
  • #97499 fix(state): refuse destructive restore on incomplete holder scans · stale or abandoned
Closed issues · 1
  • Closed#95763[Bug]: /snapshot restore prints success when the DB restore was refused
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.00 means 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 Lab

At a glance

Subsystem
hermes cli
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/95763.json
cluster/95763.md