Cairn
NousResearch/hermes-agent

writable_schema safety and connection state fixes

Cluster 86517 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 issues address bugs where writable_schema=ON could be left set on a long-lived write connection after errors, along with related WAL probe, locking, and read-pool recovery fixes. A common thread is ensuring connection state is properly reset even when operations fail.

Open issues1

  • Issue#86517state_search: writable_schema=ON window without try/finally leaves the long-lived write connection degraded on error

Open PRs1

  • PR#86708fix(state): reset writable_schema after failed legacy FTS demote

1 PR closed without merging

From the close comments: other 1

  • #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.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.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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/86517.json
cluster/86517.md