-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Botocore 1.35.45
breaks S3:SelectObjectContent
#3284
Comments
+1 seeing the same issue, breaking a lot of stuff |
Thanks for reporting this issue, we were able to reproduce this in 1.35.45. A fix is pending release here: #3285. |
This should now be fixed in version 1.35.46. Please try updating your version of boto3 and let us know if you're still running into any issues. |
should that reproduction case be added as a regression test? |
The team does plan to add a regression test for this in the near future but wanted to first release the fix in 1.35.46. |
@tim-finnigan This is still broken in version 1.35.46 - no longer for Here's another simple example:
I think the new handler that was added isn't guarding against all of the ways in which a valid/successful I'm a little surprised that this change didn't break something in your comprehensive test suite... is there really no test covering an |
@bpandola what specific error are you getting, and did that same code work prior to 1.34.45? |
@tim-finnigan Yes, that code works fine prior to 1.34.45. Running it with 1.34.46 results in a 500 error after max retries because the new S3 handler changes the status code to a 500 after trying (and failing) to parse the valid JSON response as XML. |
Thanks for following up — I'm going to close this as the SelectObjectContent issue was fixed in 1.35.46, and we can track the GetBucketPolicy/related issues in the #3286. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Describe the bug
The S3 action
SelectObjectContent
fails with the latest version of botocore. An exception is raised in the recently-added_handle_200_error
handler (see PR #3276).Regression Issue
Expected Behavior
Confirmed working in previous version(s) of botocore.
Current Behavior
Reproduction Steps
Possible Solution
The new handler has a guard clause checking if
operation_model.has_streaming_output
but it may also need to guard againsthas_event_stream_output
.Additional Information/Context
No response
SDK version used
1.35.45
Environment details (OS name and version, etc.)
MacOS, Python 3.11
The text was updated successfully, but these errors were encountered: