Fix WAL append errors and unsafe shared connection reads
Cluster 85079 · agent. Data as of
Nothing open on GitHub. Fix merged in #99502 on 31 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 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 items address retry logic for a specific WAL append error and eliminate unsynchronized reads on a shared SessionDB writer connection that could cause crashes or SystemErrors.
Open issues0
Open PRs0
Fixes on record
-
#99502 fix(state): eliminate unsynchronized reads on the shared SessionDB writer connection (SIGSEGV / SystemError class)
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
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#85065 fix(state): retry 'returned NULL without setting an exception' on WAL append · superseded by another PR →
#85079
Closed issues · 1
- Closed#85079fix(state): retry 'returned NULL without setting an exception' on contended WAL append
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.00means 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 LabAt a glance
- Subsystem
- agent
- Merged PRs
- #99502
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 31 Aug 2026