-
Notifications
You must be signed in to change notification settings - Fork 481
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
fix(s3): parse MultipartUploadResponse to check error in body #4735
Conversation
Signed-off-by: Ruihang Xia <waynestxia@gmail.com>
Signed-off-by: Ruihang Xia <waynestxia@gmail.com>
Signed-off-by: Ruihang Xia <waynestxia@gmail.com>
Signed-off-by: Ruihang Xia <waynestxia@gmail.com>
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.
Thanks a lot!
It seems hard to downstream users to know the actual result, the error in body is discared before this method returns. |
Then let's try to run a 0.47.1 release. But the unaligned version number among release artifactes is quite painful to bump ... |
I'm willing to run this release. |
S3 may return an error when the HTTP code is 200. Like this https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html#API_CompleteMultipartUpload_Example_4
This patch defines a
MultipartUploadResult
result which only contains error's definition. It will be deserialized on complete multipart upload's 200 result, to check if the body contains any error.For more background reference to awslabs/aws-sdk-rust#1163