Stream can hang if there is an error reading a source file from S3 about fs2-aws HOT 3 CLOSED

Thank you for using this library, it would be great if you create PR so we can merge this change to mainline. Or i can revisit it little bit later, this problem worth to fix, thank you again for creating the issue this makes this library better.

from fs2-aws.

I've experimented with the v3 API and the problem persists. The workaround for v3 is:

fs2.io.readInputStream(
          blocker.blockOn(IO(
            S3Client.create.getObject(
              GetObjectRequest
                .builder()
                .bucket(bucket)
                .key(key)
                .build()
            )
          )),
          chunkSize = 4096,
          closeAfterUse = true,
          blocker = blocker
        )

from fs2-aws.

As far as I can tell, it seems this issue has been resolved. Tested today, and discovered through testing that running s3.readFile (method name appears to have changed since creation of this issue) on a path which does not exist in S3 results in the exception NoSuchKeyException being returned, rather than the process hanging as described above. If this is not the case, is there any additional context surrounding the issue which may be useful in resolving it? Or if this issue has been resolved, may this issue be closed? Steps I performed in reaching this conclusion:

1. Set up S3 environment via localstack.
2. Create test in S3Suite which should fail in the above specified conditions--added a file key which did not exist.
3. Test fails, but returns an exception (NoSuchKeyException) rather than an empty stream.

from fs2-aws.