NousResearch/hermes-agent

WAL generation lost on gateway service restart

Cluster 104451. 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 and fixes concern a bug where restarting the gateway service deletes or fails to preserve the WAL generation, potentially stranding a live writer with a sticky error. The work focuses on preserving WAL state across restarts.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 1 · other 1

  • #104487 fix(gateway): preserve WAL generation during service restart · other → #104451
  • #104528 fix(gateway): preserve WAL during service restarts · duplicate → #104487
Closed issues · 1
  • Closed#104451[Bug]: hermes update partial fleet restart strands a live writer on a deleted WAL generation (sticky DeletedWalGenerationError, macOS)
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.