Cairn
NousResearch/hermes-agent

Concurrent write corruption in state.db

Cluster 73411 · agent. 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 items address state.db corruption caused by multiple processes writing simultaneously, with fixes involving gateway instance guards and cross-process file locking for WAL checkpoints.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #73534 fix(state): guard periodic WAL checkpoints with cross-process flock · superseded by another PR → fbd5e57, fe43165, #73411
  • #73721 fix(gateway): prevent state.db corruption from concurrent gateway instances · done elsewhere → fbd5e57, fe43165, #73411
Closed issues · 1
  • Closed#73411state.db corruption from concurrent `hermes serve` + `gateway run` writers on the same default profile (Linux, single host)
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
agent
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/73411.json
cluster/73411.md