Wait on Telegram group flood limits and skip forbidden chats - #1102
Closed
iFixRobots wants to merge 2 commits into
Closed
iFixRobots wants to merge 2 commits into
iFixRobots wants to merge 2 commits into
Conversation
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
1 participant
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.
I traced the issue to the SDK rageshake:
sdk.log.gz:17027-17031, 17209-17227shows a room-creationFLOOD_WAIT (3), followed by the update manager exiting and the account enteringUNKNOWN_ERROR. Telegram became unusable. The log also shows repeatedChatForbiddenfailures atsdk.log.gz:13434-13438.Wait and retry on Telegram flood limits, bounded to five attempts. Skip forbidden chats in event handling and dialog sync so one inaccessible group does not stop other updates.
Tag
@indentto continue the conversation here.