Closed dimonnwc3 closed 2 months ago
increase the stack trace limit with https://nodejs.org/api/errors.html#errorstacktracelimit.
I tried but nothing is changed
Hi @dimonnwc3 ,
What you are describing here is not unique to the SDK. This is known limitation of NodeJS as explained here. This is a common challenge with async programming in JS and is due to v8's zero cost async stack traces.
You can try running your application with $ node --async-stack-traces codeSnippet.js
to see if it solves your problem.
Since this is not an SDK issue, and not actionable by the SDK team Im going to go ahead and close this issue.
Thanks for taking the time and reaching out.
All the best, Ran~
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
While using aws s3 send method, with any command producing the error. Error stack trace points to some internal AWS library code rather than application code where send methid is called.
SDK version number
@aws-sdk/client-s3@3.552.0
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
v21.6.2
Reproduction Steps
call s3 client send method with any command that throws an error
for example:
Observed Behavior
here is example stack trace, which shows some internal of the library, but doesn't include my application code
Expected Behavior
I expect stack trace to show where error happens in my application code
example when I throw error by myself, stack trace shows exact error in my code
Possible Solution
No response
Additional Information/Context
No response