fix(telegram): classify and dedup post-reconnect probe failures (#63243) - #64368
Merged
Merged
Conversation
This was referenced Jul 14, 2026
1 task
14 tasks
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 #63247 (CI blocked for first-time contributor). Fixes #63243 — the post-reconnect probe () routed every failure into with no classification, bypassed the in-flight guard, and logged raw error text.
Changes
Attribution
Cherry-picked from @SilentKnight87's #63247 with authorship preserved.
Validation
51 passed (telegram network reconnect + pending update probe). ruff + py_compile clean.