Cairn
NousResearch/hermes-agent

Kanban SQLite connection and WAL file descriptor leaks

Cluster 29610 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

Most members concern SQLite connections in the Kanban database or dispatcher not releasing file descriptors, especially in WAL mode, with reports of 'Too many open files' on macOS. The pull requests propose varied approaches, such as closing connections, adding close() methods, and connection pooling, and one also mentions an FTS5 fallback.

Open issues0

No open issues.

Open PRs0

No open pull requests.

5 PRs closed without merging

From the close comments: done elsewhere 4 · superseded by another PR 1

  • #31130 fix(kanban-db): WAL file descriptor leak on connect/close cycles (fixes #30799) · done elsewhere → ebe04c6, #30799, #31158
  • #32135 fix(kanban): close decomposer SQLite connections · done elsewhere → ebe04c6
  • #33927 fix(kanban): add connection pooling to prevent FD exhaustion · done elsewhere → ebe04c6
  • #36116 fix(db): close() methods on SQLite classes + WAL FD leak fix · superseded by another PR → ebe04c6
  • #67389 fix(db): close SQLite FDs on context exit and fallback gracefully if FTS5 is missing · done elsewhere → b405c39, 5eb5583, 0773b66, 99e1d39
Closed issues · 4
  • Closed#29610Bug: embedded Kanban dispatcher still leaks sqlite/WAL file descriptors after #28301
  • Closed#30799kanban dispatcher FD leak: SQLite connections not releasing file descriptors in WAL mode
  • Closed#31736Gateway embedded Kanban dispatcher opens SQLite WAL connections every tick, causing FD/WAL pressure
  • Closed#33580kanban_db.py: connection leak causes 'Too many open files' on macOS (FD exhaustion)
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.20: 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
gateway
Closed issues
4
Attempts
5 PRs closed without merging

For your agent

The same facts, typed.

cluster/29610.json
cluster/29610.md