Telegram gateway event-loop blocking and deaf-socket bug
Cluster 111727. Data as of
Nothing open on GitHub. Fix merged in #112201 on 16 Sep 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 #112201. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where the Telegram gateway's sockets enter CLOSE-WAIT while falsely reporting connected, spinning CPU, and blocking getUpdates polling; the related fixes address typing re-arm scheduling to avoid pinning the event loop.
Open issues0
Open PRs0
Fixes on record
-
#112201 fix(telegram): streaming replies no longer pin the event loop on typing re-arms, so getUpdates polls stop going deaf (#111727, salvage #111886)
files:
contributors/emails/[redacted:email],plugins/platforms/telegram/adapter.py,tests/gateway/test_telegram_typing_retrigger.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#111886 fix(telegram): schedule the post-send typing re-arm instead of awaiting it · merged via another change →
3250020,#112201
Closed issues · 1
- Closed#111727[Bug]: Telegram gateway silently goes deaf (sockets stuck in CLOSE-WAIT) while reporting "connected", and spins ~1 core
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
- #112201
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 16 Sep 2026