Cairn
NousResearch/hermes-agent

Force GC after retiring OpenAI clients to free FDs

Cluster 80792 · 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 items address a file descriptor leak where retiring shared OpenAI clients defers socket/FD release until garbage collection, proposing or applying an explicit gc.collect() call as a fix. The issue manifests as EMFILE errors in long sessions with provider fallbacks.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 1 · other 1

  • #80853 fix(agent): force GC collect after retiring shared OpenAI client · other → #80792
  • #80918 fix(agent): trigger gc.collect() after retiring shared OpenAI clients (#80792) · duplicate → #80853, #80792
Closed issues · 1
  • Closed#80792EMFILE (too many open files) in long sessions with provider fallbacks — _retire_shared_openai_client defers FD release to GC
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.

cluster/80792.json
cluster/80792.md