-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
TypeError: self._handler is not a function in @sentry/node 5.15.5 #2599
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.
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
Comments
Detected the same issue on @sentry/node 5.15.5. Downgraded to 5.15.4 as a workaround. |
There was no changes done to node package between |
Also getting this with sentry/node 5.18.1:
|
Looks like
|
Can confirm the crash is still present in
|
Another stack trace:
It seems that this happens whenever Sentry tries to log an error, and then this appears in Sentry instead of the actual error. |
Have recently installed 7.8.0 from 6.16.1 and this issue seems to have returned. Seeing identical behaviour to that described in this thread. It looks like this commit re-introduced the problem perhaps? 4077204#diff-e61f0c3774e88d33bd71fe7da37672a7702f0859aaa3d0a65b5f543b7af778daL48 The specific stack trace we get is
Event ID |
Package + Version
@sentry/browser
@sentry/node
raven-js
raven-node
(raven for node)Version:
Description
When using the Express error handler (
Sentry.Handlers.errorHandler()
) and throwing an error inside a route, it doesn't get captured by Sentry, instead a crash inside the library appears.Downgrading to
5.14.2
fixes it and the exception appears in Sentry as expected.Event ID
60a596ee9f9848299273f60b8fb524ef
to see an example.The text was updated successfully, but these errors were encountered: