-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
Error: ETag does not match MD5 checksum #23
Comments
I'm seeing the exact same thing. It started happening to me when I changed the target bucket to be encrypted. |
I've traced this through a little. This module depends on the @monolambda fork of Wonder if @monolambda would consider merging andrewrk/node-s3-client#166 into their fork and releasing? Then we can update this module to incorporate the fix? |
Hi there. Was this issue ever fixed and released in newer versions? |
I just got this error today so I don't think it's been fixed. |
I got this too. Is not fixed. |
Error: ETag does not match MD5 checksum
I am seeing the following error when using this module. I see that the files sync to s3 just fine, however this error still occurs while the 'S3 Sync: Syncing directories and S3 prefixes' is occurring. The error seems to be random when it occurs. 85% of the time it is occurring. It seems like an error that doesn't mean anything related the syncing, because the syncing still happens and looks fine. This happens on both encrypted and unencrypted buckets.
The text was updated successfully, but these errors were encountered: