aws
test(#300): @NathanEckert is correct
The modern S3EC and SDK V2 treat reading 0 bytes from a stream differently in at least one case: If the Stream has no more content.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Check any applicable:
- [ ] Were any files moved? Moving files changes their URL, which breaks all hyperlinks to the files.
Side Note: I have no idea why the CRT tests are taking so long... CI this morning took 8 minutes: https://github.com/aws/amazon-s3-encryption-client-java/actions/runs/9647714113/job/26607177101. But every test run I have started has timed out, with the tests stalling on the CRT.
Maybe these are related?
This is a good PR to have once the upstream issue has been fixed. This can be used to verify that everything is GTG.
