fix: use asyncio.sleep for non-blocking delay in RetryHandler #485
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
|
baywet
approved these changes
Jul 18, 2025
Member
baywet
left a comment
baywet
left a comment
There was a problem hiding this comment.
Thank you for the contribution!
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.
Overview
The RetryHandler previously used
time.sleep(delay)to pause between retries. However,time.sleepis a blocking call and can halt the entire async event loop, which negatively impacts asynchronous applications like FastAPI.This PR replaces
time.sleep(delay)withawait asyncio.sleep(delay), ensuring that the sleep is non-blocking and the event loop remains responsive during retry delays. This change improves compatibility and performance in asynchronous environments.Related Issue
N.A
Demo
N.A
Notes
N.A
Testing Instructions
All existing Tests pass