Telegram transport pool reset and connection leak
Cluster 82920. Data as of
Nothing open on GitHub. Fix merged in #83044 on 10 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #83044. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #83044. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a bug where Telegram's fallback-IP transport bypasses HTTP connection limits causing CLOSE_WAIT socket leaks, and associated corrections to reset the primary transport pool when it enters an error state.
Open issues0
Open PRs0
Fixes on record
-
#83044 fix(telegram): reset failed primary transport pool
files:
plugins/platforms/telegram/telegram_network.py,tests/gateway/test_telegram_closewait_limits_31599.py,tests/gateway/test_telegram_fallback_pool_release_71593.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#83001 fix(telegram): reset failed primary transport pool · merged via another change →
#83044
Closed issues · 1
- Closed#82920[Bug]: Telegram fallback-IP transport bypasses platform_httpx_limits() — CLOSE_WAIT leak (~18/hr) → EMFILE when no fallback_ips are configured
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.00means 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 LabAt a glance
- Merged PRs
- #83044
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 10 Aug 2026