-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
SImpleDB stopped working after upgrade #3055
Comments
Ah, we also tried to upgrade to simpledb 1.49.0, but it didn't help |
Thanks for opening an issue. This is likely broken in core 3.192.0 (can you confirm?) where some sweeping protocol changes were made. SimpleDB is effectively deprecated - no new accounts can even see it in the console. I can consider a fix for it if we can diagnose it (I can't, because I don't even have access to the service) but the likely situation is that you should pin your version to 3.191.0 and move to dynamodb or some other data store. New aws-sdk-simpledb versions have only been published because of code generation changes and not any API changes. Can you enable |
Pinned the module and it helped. As for http_wire_trace, not sure where to put it, but since it's "effectively deprecated" we can start working on migrating away. |
Apologies, |
Unless we find the root cause and it's an easy fix, I'll unfortunately mark this as "wontfix" given SimpleDB's posture. I'm very sorry that our change broke you. Please re-open with new information if you have any, and any questions you may have about using DynamoDB. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
I was able to get an account to reproduce and I think I have a fix for you. #3056 It should be released maybe Monday or Tuesday. @depesz Can you verify the fix? You can pull the latest core and then apply this monkey patch
|
SUCCESS! First did:
Then modified /var/lib/gems/2.7.0/gems/aws-sdk-simpledb-1.49.0/lib/aws-sdk-simpledb/client_api.rb with your changes, and now my script works without pinning to old core/simpledb. Thanks a lot :) |
Fix went out with the latest most recent version of |
Describe the bug
We had gem versions:
And our script worked great.
Yesterday, for some reason core was upgraded to 3.199.0 and our script no longer works.
Expected Behavior
put attribute should work
Current Behavior
raises exception:
Reproduction Steps
Well, it would require some connection details, but generally the line that causes the error haven't changed in years, and looks like:
Possible Solution
No response
Additional Information/Context
No response
Gem name ('aws-sdk', 'aws-sdk-resources' or service gems like 'aws-sdk-s3') and its version
aws-sdk-core 3.199.0
Environment details (Version of Ruby, OS environment)
ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [aarch64-linux-gnu]; Ubuntu focal
The text was updated successfully, but these errors were encountered: