-
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
DynamoDB: Unable to put binary data #831
Comments
Thanks for this, I was able to reproduce and I'm taking a look. |
I have a possible fix written which passes in your case, but there are a few other cases I want to check in review. Will push up my changes to a branch and PR. |
awood45
added a commit
that referenced
this issue
Jun 2, 2015
Resolves Issue #831 Running the following code exercised the problem, and now works with this change: ``` dynamodb.put_item( table_name: "foo", item: { id: 1, contents: StringIO.new("bar") } ) ``` The issue appeared to be that #read was called twice on the StringIO or IO object, and the second call would fail as String#read does not exist.
Closed by #832 |
Thanks for version 2.0.48! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying to put binary data to DynamoDB, I get an exception regarding the usage of an IO (eg.
StringIO
) type. I'm using the actual gem (2.0.47).Simple example to reproduce:
Exception and backtrace:
The text was updated successfully, but these errors were encountered: