NousResearch/hermes-agent

state.db multi-writer corruption and detection fixes

Cluster 100896. 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.

A bug report and two fixes addressing SQLite WAL corruption caused by multiple processes simultaneously writing to state.db. Work covers detection of concurrent writers at open time and prevention of writer multiplication during startup.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: stale or abandoned 1 · other 1

  • #100958 fix(state): stop concurrent startup from multiplying state.db writers · stale or abandoned → #101191, #100896, #100767
  • #102663 fix(state): detect multi-process WAL writer set at state.db open · other → 902ecca, #108076
Closed issues · 1
  • Closed#100896[Bug] state.db corruption x4 in 5 weeks (gateway+dashboard multi-writer WAL) — "5 live SessionDB handles" warning fires 7 min before onset; journal_mode=delete containment
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

Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.