Move pagination into asyncio.to_thread#238
Merged
Merged
Conversation
TheByronHimes
approved these changes
Jul 7, 2026
TheByronHimes
left a comment
TheByronHimes
left a comment
Member
There was a problem hiding this comment.
LGTM, but I think a template update is required now
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.
Currently the pagination and related IO accidentally happen synchronously on the main thread.
This PR moves the corresponding callsites completely into
asyncio.to_threadwhich should correctly dispatch them on separate threads.As a performance optimization,
_list_multipart_uploads_for_objectnow uses aPrefix=object_idfilter. This works for the current setup, but will break if we ever change any functionality that creates an object to use anything else thanKey=object_id.