fix(gateway): quiet noisy Telegram errors and sanitize provider failures#28533
Merged
Conversation
Contributor
🔎 Lint report:
|
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
2 participants
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.
Salvage of #24014 (@houenyang-momo). Adds Telegram-specific gateway filtering for noisy lifecycle/status callbacks (auxiliary title/compression failures, retry backoff chatter). Sanitizes Telegram-facing provider/API failures so raw HTTP bodies, policy/security text, request IDs, and key-like values aren't sent to chat. Suppressed callbacks still logged with secret redaction.
Conflict resolution: combined the new
_prepare_gateway_status_messagefilter with the just-mergedsafe_schedule_threadsafescheduler pattern (HEAD).Authorship preserved via cherry-pick. 38/38 noise-filter + display-config tests passing.