-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
update ASF APIs, fix SQS serialization #9611
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
Conversation
LocalStack Community integration with Pro 2 files ±0 2 suites ±0 1h 19m 9s ⏱️ + 10m 58s Results for commit 4fa3c90. ± Comparison against base commit 9dc7713. This pull request removes 1 and adds 2 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
a8b3536
to
49b84a7
Compare
Test run in ext validating SQS changes: 6850081041 |
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 @bentsku for jumping on this last piece to get the JSON protocol changes in SQS over the line! 🦸🏽
-ext tests are green! just waiting for the last one in CircleCI and we can merge. |
The failing tests are flakes, everything else is green (and the tests were successful in another run), so I'll move forward and merge this one. |
Motivation
This PR started out as a regular automatically created ASF Update PR, but it contains some crucial changes in the SQS specs related to #8268 and #8267.
These recent changes in
botocore
have quite an impact on the generated ASF API stubs (see the first commit in this PR).These changes need to be addressed in the SQS serializers to make sure that the responses (especially the error codes) are serialized properly.
Changes
Integer
toNullableInteger
, even though within the shape itself is not nullable, the presence of the field is optional).