# NousResearch/hermes-agent · Telegram fallback pool FD budget cap fix

## Open now

- 1 issue, 0 PRs open on GitHub.
- #82678: Telegram fallback path can exceed the process FD budget through uncapped 512-connection pools

These items address a bug where Telegram's fallback connection pools could exceed the process file descriptor budget due to uncapped 512-connection pools. The fix bounds the fallback-pool connection budget by the pool count.

## 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

- #82678: Telegram fallback path can exceed the process FD budget through uncapped 512-connection pools

## Prior & competing PRs

- **#82860: fix(telegram): bound fallback-pool connection budget by pool count**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`
- **#127816: fix(telegram): bound fallback-pool connection budget by pool count**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`

## Fix status

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