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.

Sign up for GitHub

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

Jump to bottom

Investigation: WriteGetObjectResponseAsync does not throw proper error message for non-seekable streams #2524

Open
ashishdhingra opened this issue Jan 20, 2023 · 0 comments
Open

Investigation: WriteGetObjectResponseAsync does not throw proper error message for non-seekable streams #2524

ashishdhingra opened this issue Jan 20, 2023 · 0 comments
Labels
bug This issue is a bug. p2 This is a standard priority issue queued s3

Comments

@ashishdhingra
Copy link
Contributor

Describe the bug

Related issue: #2519

Based on the discussion with the team, we need to investigate the exception message that is thrown when WriteGetObjectResponseAsync() is used with non-seekable streams.

Expected Behavior

Proper error message should be thrown that the stream is not seekable, rather than generic SigV4 error.

Current Behavior

Exception Amazon.Runtime.AmazonClientException: ChunkedUploadWrapperStream was initialized without a SigV4 or SigV4a signing result. is thrown.

Reproduction Steps

Refer #2519 (comment)

Possible Solution

No response

Additional Information/Context

No response

AWS .NET SDK and/or Package version used

AWSSDK.S3 3.7.101.48
AWSSDK.Core 3.7.103.10

Targeted .NET Platform

.NET 6

Operating System and version

Windows 10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug This issue is a bug. p2 This is a standard priority issue queued s3
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ashishdhingra