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

amazonka-core: fix body length calculation in hashedFileRange #794

Merged
merged 1 commit into from
Jun 29, 2022

Conversation

endgame
Copy link
Collaborator

@endgame endgame commented Jun 29, 2022

@axman6

Fixes #548

@endgame endgame added this to the 2.0 milestone Jun 29, 2022
@endgame endgame force-pushed the hashed-file-range-correct-size branch from 4366a09 to f86336c Compare June 29, 2022 09:43
@endgame
Copy link
Collaborator Author

endgame commented Jun 29, 2022

@axman6 and I spent an evening shuffling large files between EC2 and S3 while fixing up amazonka-s3-streaming so we're pretty sure that this is good.

@endgame endgame merged commit 0d70474 into brendanhay:main Jun 29, 2022
@endgame endgame deleted the hashed-file-range-correct-size branch June 29, 2022 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

hashedFileRange results in WrongRequestBodyStreamSize
1 participant