Skip to content
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

Fixes DynamoDB response data for CRC32CheckFailed error #983

Merged
merged 1 commit into from
May 4, 2016

Conversation

LiuJoyceC
Copy link
Contributor

@LiuJoyceC LiuJoyceC commented May 3, 2016

Fixes bug in which response data is not null when DynamoDB returns a CRC32CheckFailed error. Response data will now return null when error occurs. Fixes #981
/cc @chrisradek

…CRC32CheckFailed error. Response data will now return null when error occurs.
@coveralls
Copy link

coveralls commented May 3, 2016

Coverage Status

Coverage increased (+0.003%) to 88.543% when pulling 4b6034f on LiuJoyceC:dynamoCrc32ErrorDataNull into 0529f39 on aws:master.

@chrisradek
Copy link
Contributor

:shipit:

@LiuJoyceC LiuJoyceC merged commit 7fa350c into aws:master May 4, 2016
@LiuJoyceC LiuJoyceC deleted the dynamoCrc32ErrorDataNull branch May 4, 2016 22:29
LiuJoyceC added a commit that referenced this pull request May 5, 2016
@lock
Copy link

lock bot commented Sep 28, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked as resolved and limited conversation to collaborators Sep 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CRC32 check failed, marked as retryable but actually request will not be repeated
3 participants