# NousResearch/hermes-agent · Telegram polling stuck retrying, socket exhaustion fixes

## Open now

- 1 issue, 0 PRs open on GitHub.
- #69314: \[Bug\]: Telegram gateway behind healthy HTTP proxy gets stuck retrying with hundreds of CLOSE_WAIT sockets until full restart

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.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Open related issues

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

## Prior & competing PRs

- **#68983: fix(telegram): recover exhausted request pool**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#98094`
- **#126350: fix(telegram): disarm PTB retry loop on polling network error recovery**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`