[BUG] empty messages for unhandled promise rejections
See original GitHub issueDescription/Screenshot
message
is passed as theEvent
from Exception.CreateAutoException
. Should evt
been passed instead? And/or should you fall back to theEvent
if it’s a string
?
Results in these empty error messages, so I don’t see the actual error.
- SDK Version: 2.6.4
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:8 (5 by maintainers)
Top Results From Across the Web
What is an unhandled promise rejection? - Stack Overflow
A rejected promise is like an exception that bubbles up towards the application entry point and causes the root error handler to produce...
Read more >Unhandled Promise Rejections in Node.js - The Code Barbarian
If you want to suppress the unhandled promise rejection warning, all you need to do is call .catch() on the promise with an...
Read more >Handling those unhandled promise rejections with JS async ...
If all you want is to terminate the script and display the error, you can simply get rid of the try/catch block altogether....
Read more >Process | Node.js v19.3.0 Documentation
Rejections can be caught and handled using promise.catch() and are propagated through a Promise chain. The 'unhandledRejection' event is useful for detecting ...
Read more >Best Practices for Node.js Error-handling - Toptal
This article will introduce you to error-handling in Node.js and ... It is not hard to see warning messages about unhandled promise rejections...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sounds good, thanks for jumping on that. I’ll just downgrade for now. When do you think that’ll be released?
Fwiw, my stack trace also was empty. Looking at the code it looks like it would’ve used
error.stack
, so not sure why that happened. But I’ll let you know if I find anything.No
Yes