-
Notifications
You must be signed in to change notification settings - Fork 116
Wait for running parts before aborting multipart uploads, and validate S3File before init #992
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
b2c0fe7
Wait for running parts before aborting, and validate S3File before init
laughingman7743 0191c1f
Wait for the running function in the loop shutdown test
laughingman7743 35b07a9
Do not wait for cancelled parts, and settle aio futures exactly once
laughingman7743 5060d5a
Release the running part from the wait in the abort ordering tests
laughingman7743 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Self-review round 2 (claims, callers, operations) — FINDINGS (PR description corrected; no code change)
Scope:
git diff aa0fc9146f4e683d6cdf96b894f963f9dd8f7abe..0191c1f683ff6ee0283d4cbdf431ecb8f876b87b, the PR body, commit messages, changed docstrings/comments, anddocs/filesystem.md.Claims checked:
uv.lock.super().__init__. Reproduced on aa0fc91: the issue script prints one "Exception ignored" line (the block size file), not two. Corrected the WHY section; the missing-key test cases pass on the base and are kept for the no-request contract.open()/put_file()withdefault_block_size> 5 GiB now fail atopen()even for small writes that used to succeed with a single PutObject;pipe_file()of data that fits in one PutObject never opens a file and is unaffected (s3.pypipe_fileroutes onmin(block_size, MULTIPART_UPLOAD_MAX_PART_SIZE)). Added this to the release-note items. Read-mode block sizes (e.g.S3FSResultSet'sdefault_block_size) are not checked._call's retry configuration, as the part request itself already was; stated in the release note. No new requests are added.docs/filesystem.md: no other statement about block size limits exists indocs/or the README.