fix(telegram): require getUpdates progress before polling is healthy - #64381
Merged
Merged
Conversation
kshitijk4poor
force-pushed
the
fix/63581-salvage
branch
from
July 14, 2026 12:00
fd74569 to
5dc3fd5
Compare
kshitijk4poor
enabled auto-merge (rebase)
July 14, 2026 12:10
7 tasks
For PR NousResearch#63581 salvage (telegram: require getUpdates progress before polling is healthy).
kshitijk4poor
force-pushed
the
fix/63581-salvage
branch
from
July 14, 2026 12:12
5dc3fd5 to
bc5943e
Compare
This was referenced Jul 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Salvage of #63581 (CI blocked for first-time contributor). Makes Telegram polling health depend on successful getUpdates progress rather than get_me() return. PTB's Updater.start_polling() can return after creating its retry task but before the first getUpdates request succeeds — a cold start or reconnect could log "Connected", clear degraded send protection, and remain alive-but-deaf indefinitely.
Changes
Attribution
Cherry-picked from @arnispiekus's #63581 with authorship preserved. Built on top of #63247 (SilentKnight87) which was merged via #64368.
Validation
AUTHOR_MAP
Added arnispiekus mapping in a separate chore commit (required for check-attribution).