SessionDB duplicate-writer warning excludes invalid handles
Cluster 113637. Data as of
Nothing open on GitHub. Fix merged in #114916 on 18 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #114916. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #114916. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests address a bug where the SessionDB duplicate-writer warning incorrectly counted closed, read-only, or partially initialized handles. The fixes narrow the count to only live, writable handles.
Open issues0
Open PRs0
Fixes on record
-
#114916 fix(state): duplicate-writer warning no longer counts closed or half-built SessionDB handles (#113637, salvage #113642)
files:
hermes_state.py,hermes_state_readpool.py,tests/hermes_state/test_session_db_read_conn_pool.py
2 PRs closed without merging
From the close comments: duplicate 1 · merged via another change 1
Closed issues · 1
- Closed#113637[Bug]: SessionDB duplicate-writer warning counts read-only and closed handles
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.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
- Merged PRs
- #114916
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 18 Sep 2026