Cairn
NousResearch/hermes-agent

Telegram polling stuck retrying, socket exhaustion fixes

Cluster 69314 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

These items address a bug where the Telegram gateway gets stuck in retry loops and accumulates CLOSE_WAIT sockets during network error recovery. The fixes target the PTB retry loop behavior and request pool exhaustion under these conditions.

Open issues1

  • Issue#69314[Bug]: Telegram gateway behind healthy HTTP proxy gets stuck retrying with hundreds of CLOSE_WAIT sockets until full restart

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: superseded by another PR 1 · other 1

  • #68983 fix(telegram): recover exhausted request pool · superseded by another PR → #98094
  • #126350 fix(telegram): disarm PTB retry loop on polling network error recovery · 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
gateway
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/69314.json
cluster/69314.md