Closed piurafunk closed 1 month ago
Hi @piurafunk ,
Thanks for your patience. Im able to reproduce the reported behavior. It's not clear to me at this point why an error is not thrown by the SDK. Will review this and let you know.
Thanks, Ran~
fix included in https://github.com/aws/aws-sdk-js-v3/pull/6112
should be released in https://github.com/aws/aws-sdk-js-v3/releases/tag/v3.582.0 tomorrow
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.
Checkboxes for prior research
Describe the bug
Exceeding
Upload.MAX_PARTS
doesn't throw an exception completely outSDK version number
@aws-sdk/client-s3@3.549.0
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
v20.12.0
Reproduction Steps
Observed Behavior
The object size is actually exactly 5 MiB x 10,000 parts: 52428800000 bytes. Notably, it also correctly completes the multi-part upload, so it really does look like it completes.
I also tested with
await upload.done().catch(err => {throw err})
in case of promise being rejected; it has the same problem.Expected Behavior
https://github.com/aws/aws-sdk-js-v3/blob/v3.549.0/lib/lib-storage/src/Upload.ts#L195 should throw an exception out when the parts max is exceeded.
Possible Solution
I'm not a node expert, but I suspect it has something to do with throwing an error inside an async function.
Additional Information/Context
No response