# NousResearch/hermes-agent · SessionDB duplicate-writer warning excludes invalid handles

## Open now

- 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.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #114916. Verify it addresses your case.
- **Recommended:** read PR #114916 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-114916`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.50`: the share of member 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.

## Closed / duplicate issues

- #113637: \[Bug\]: SessionDB duplicate-writer warning counts read-only and closed handles

## Prior & competing PRs

- **#114916: fix(state): duplicate-writer warning no longer counts closed or half-built SessionDB handles (#113637, salvage #113642)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_state.py`, `hermes_state_readpool.py`, `tests/hermes_state/test_session_db_read_conn_pool.py`
- **#113642: fix(state): exclude closed SessionDB writers from warning**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `daa2f96d8c9a`, `#114916`, `#113637`, `#113642`
- **#113857: fix(sessiondb): count only live writable handles in duplicate-writer warning**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#113642`

## Fix status

- Merged to main in PR #114916 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-18`.