NousResearch/hermes-agent

SessionDB file descriptor leak in react_to_message

Cluster 83072 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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
Nothing open on GitHub.

These issues and PRs address a file descriptor leak caused by react_to_message not closing its dedicated SessionDB after each call. Work also covers hardening SessionDB handling, vision routing, and test isolation.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1

  • #83079 fix: harden SessionDB, vision routing, and test isolation · done elsewhere → #83072, #83226, #83097, #92167, #83089, #92168, #83095, #92169
  • #83885 fix(desktop): close SessionDB in react_to_message tool to stop FD leak · duplicate → #83079
Closed issues · 1
  • Closed#83072react_to_message leaks its dedicated SessionDB on every call
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
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.