Cairn
NousResearch/hermes-agent

Fix unsynchronized SessionDB reads causing crashes

Cluster 86516 · agent. Data as of

Nothing open on GitHub. Fix merged in #99502 on 31 Aug 2026. Check it covers your case.

The short answer

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

These issues and patches address multiple read paths in SessionDB that bypass locking and the read context, accessing the shared writer connection without synchronization. The fixes route reads through the proper context and connection pool to prevent dirty reads and crashes such as SIGSEGV and SystemError.

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.

  • #99502 fix(state): eliminate unsynchronized reads on the shared SessionDB writer connection (SIGSEGV / SystemError class)

    merged to main

    files: hermes_state.py, hermes_state_search.py, tests/state/test_writer_conn_thread_safety.py, tests/test_hermes_state_conn_lock_audit.py, tests/test_session_db_read_path_split.py

2 PRs closed without merging

From the close comments: merged via another change 1 · other 1

  • #87612 fix(state): WAL probe fallback, bare-SELECT locking, writable_schema finally, read-pool self-heal · other
  • #99454 fix(state): route remaining SessionDB SELECTs through _read_ctx · merged via another change → #82428
Closed issues · 1
  • Closed#86516state: four read paths bypass self._lock / _read_ctx and read on the shared write connection (dirty reads of uncommitted transactions)
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.50: 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
Merged PRs
#99502
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
31 Aug 2026

For your agent

The same facts, typed.

cluster/86516.json
cluster/86516.md