Telegram polling TCP connection reuse and port exhaustion

NousResearch/hermes-agent · cluster 107880 · gateway

Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These members address a bug where Telegram's getUpdates polling creates excessive TCP connections, exhausting ephemeral ports via TIME_WAIT accumulation on macOS and potentially other platforms. Fixes involve reusing keepalive connection pools to mitigate the issue.

Open issues1

  • Issue#107880[Bug]: Telegram polling can exhaust macOS ephemeral ports with TIME_WAIT after ~2 days

Open PRs2

  • PR#107892fix(telegram): reuse getUpdates keepalive on Darwin to avoid TIME_WAIT exhaustion
  • PR#107897fix(telegram): reuse a small getUpdates keepalive pool off Windows (#107880)
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
gateway
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.