-
Notifications
You must be signed in to change notification settings - Fork 134
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
Handle checksums on copy #242
Conversation
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.
Hi @rapkyt,
Thanks for the PR! I've left some quick feedback. Overall, I think this is looking good, just a few more changes should get it ready to ship. Please let us know if you have any questions.
I am also blocked on this PR. If possible, do we have an ETA for this to be merged? |
@nateprewitt I've made the requested changes, |
do we have an ETA for this merge? and then release? |
Hi everyone, any chance we can help get this done? The possibility of using aws' checksums is very welcome for all those doing checksums for data integrity purposes. |
This not being merged is currently blocking me. What are we waiting on @nateprewitt ? |
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.
LGTM
Requested changes were addressed by the author.
* release-0.6.1: Bumping version to 0.6.1 Handle checksums on copy (#242) Update block public access settings Use codecov-action instead of pip installing. Fix isort version (#263) Bump wheel from 0.37.0 to 0.38.1 (#261) Move CI to release 3.11 build (#259) Update lockfile to fix atomicwrite (#245) Add testing and classifier for Python 3.11 (#243)
S3.Object.copy()
fails with multipart andChecksumAlgorithm
as mentioned in #241This fixes the issue by adding the checksum information to
CompleteMultipartUpload