Cairn

WAL descriptor lifecycle and close-tolerance fixes

NousResearch/hermes-agent · cluster 110214

Data as of

Nothing open on GitHub. Fix merged in #110544. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #110544. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and pull requests address bugs where state.db WAL operations fail when descriptors are closed mid-scan, during checkpointing, or across sibling process closes. The work focuses on making WAL scanning and guard logic more tolerant of descriptor state changes without crashing or halting.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #110544 state.db WAL survives sibling closes and stray lock cancellation on every runtime (Desktop chat dies after update; salvage #109758)

    merged to main

    files: hermes_state.py, hermes_state_dbfile.py, hermes_state_lockguard.py, tests/hermes_state/test_deleted_wal_generation_guard.py, tests/hermes_state/test_wal_lock_guard.py

  • #111176 Deleted-WAL guard no longer counts a descriptor closed mid-scan as a holder (refs #110214, salvage #110235)

    merged to main

    files: hermes_state_dbfile.py, tests/hermes_state/test_deleted_wal_generation_guard.py

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #110235 fix(state): tolerate closed WAL scan descriptors · merged via another change → 7feaf03, #111176
  • #110262 fix(state): tolerate in-process WAL checkpointing and prevent read-pool descriptor accumulation (#110214) · superseded by another PR → 3e43cee, #110544
Closed issues · 1
  • Closed#110214Gateway halts hourly with 'retired state.db-wal generation' after WSL kernel update to 6.18.33
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.40: 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

Merged PRs
#110544, #111176
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
15 Sep 2026

For your agent

The same facts, typed.

cluster/110214.json
cluster/110214.md