Fix: Respect sleep_threshold=0 in invoke() to prevent unwanted Flood…#146
Open
b1rdfr0st wants to merge 1 commit intoMayuri-Chan:mainfrom
Open
Fix: Respect sleep_threshold=0 in invoke() to prevent unwanted Flood…#146b1rdfr0st wants to merge 1 commit intoMayuri-Chan:mainfrom
b1rdfr0st wants to merge 1 commit intoMayuri-Chan:mainfrom
Conversation
…Wait sleep This PR updates the `invoke()` method to correctly handle `sleep_threshold=0`. ### Before: Even when `sleep_threshold=0`, the client still waits for the full FloodWait duration. ### After: With this change: - If `sleep_threshold == 0`, it raises the FloodWait immediately (no sleep). - If `sleep_threshold < 0`, it always raises (never sleeps). - If `sleep_threshold > 0`, it only sleeps if `amount <= sleep_threshold`. This makes `sleep_threshold` behave more as expected and allows advanced bot handling logic outside of Pyrogram. Thanks!
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.
…Wait sleep
This PR updates the
invoke()method to correctly handlesleep_threshold=0.Before:
Even when
sleep_threshold=0, the client still waits for the full FloodWait duration.After:
With this change:
sleep_threshold == 0, it raises the FloodWait immediately (no sleep).sleep_threshold < 0, it always raises (never sleeps).sleep_threshold > 0, it only sleeps ifamount <= sleep_threshold.This makes
sleep_thresholdbehave more as expected and allows advanced bot handling logic outside of Pyrogram.Thanks!