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

Race condition with S3 PutObject upload stream with Netty client #24

Open
vigoo opened this issue Aug 24, 2020 · 1 comment
Open

Race condition with S3 PutObject upload stream with Netty client #24

vigoo opened this issue Aug 24, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@vigoo
Copy link
Collaborator

vigoo commented Aug 24, 2020

It fails with Data read has a different checksum than expected, but it can randomly pass if pausing it with a debugger for example.

My investigation shows that the stream gets drained and bytes sent to the Netty channel, still in the checksum validator the response metadata (from localstack) contains a different checksum and the content length is reported as 0.

There is a test case in the integtests subproject to reproduce it.

@vigoo
Copy link
Collaborator Author

vigoo commented Aug 25, 2020

NOTE: if content length is known and it's set on the request object, it works correctly.

@vigoo vigoo modified the milestones: 2.x.x.1, 3.x.x.x Aug 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant