Cairn
NousResearch/hermes-agent

Read connection pool error handling and self-healing

Cluster 86518 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These items address how the state layer's read connection pool handles broken or errored connections, including discarding pooled connections after database errors and adding self-healing behavior analogous to the write-side reconnect logic.

Open issues1

  • Issue#86518state: read connection pool never invalidates broken connections (asymmetric with write-side _reconnect_after_notadb self-heal)

Open PRs1

  • PR#99618fix(state): discard pooled read connections after DatabaseError

2 PRs closed without merging

From the close comments: superseded by another PR 1 · other 1

  • #87018 fix(state): discard pooled read connections after DatabaseError · superseded by another PR → #85255
  • #87612 fix(state): WAL probe fallback, bare-SELECT locking, writable_schema finally, read-pool self-heal · other
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
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/86518.json
cluster/86518.md