-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
Package: nodeIssues related to the Sentry Node SDKIssues related to the Sentry Node SDK
Description
Is there an existing issue for this?
- I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- I have reviewed the documentation https://docs.sentry.io/
- I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases
How do you use Sentry?
Sentry Saas (sentry.io)
Which package are you using?
@sentry/node
SDK Version
7.14.2
Framework Version
No response
Link to Sentry event
No response
Steps to Reproduce
- create new express node project from https://github.com/sentry-demos/express
- upgraded sentry to 7.14.2
- added an async request with a reject
app.get('/unhandledasync', async function () {
Promise.reject('failure to handle async')
});
- add basic error handler that will respond with 501 and possibly send an error object back
app.use((error,_req,res,next) => {
console.log('500')
res
.status(501)
.send(error)
next(error)
})
- call the async reject /unhandledasync using curl
this is a change in version 7.12
version 7.11 worked as expected
Expected Result
for sentry to call next when it received an error that is asynchronous and allow the following handler 'custom error handler) process the response
Actual Result
the exception is unhandled and the process is terminated.
when /unhandled is called the process works as expected
Metadata
Metadata
Assignees
Labels
Package: nodeIssues related to the Sentry Node SDKIssues related to the Sentry Node SDK