Cairn
NousResearch/hermes-agent

Preserving hot WAL during backup restore with damaged SQLite header

Cluster 140053 · hermes cli. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

The three members all concern backup/restore behavior when the main SQLite database header is damaged or mismatched while a readable hot WAL exists. They include a Windows post-update restore report and two fix-oriented changes, one preserving the WAL and one letting a WAL-aware probe override the header check.

Open issues1

  • Issue#140053Windows post-update restore can discard readable hot WAL after main-header damage

Open PRs2

  • PR#140055fix(backup): let a WAL-aware probe override a mismatched SQLite header
  • PR#140065fix(backup): preserve a hot WAL when the main DB header is damaged
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
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/140053.json
cluster/140053.md