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
domain.enter is not a function #1843
Comments
After upgrade to 4.5.2 we started to receive similar strange errors, and had to rollback. |
Same problem here in
|
We're also seeing "app.render is not a function" which is a very odd error that we do not understand |
Fixed in |
Hey @kamilogorek just for my own curiosity, which commit in particular fixed our issue? |
@adriaanmeuris @vvo could you please give a |
@vvo we fixed prototype inheritance, but missed one bit. Should be fixed in |
@kamilogorek sorry for the delay, but due to the many releases and bugs we've taken extra time to test before releasing on production. For now, all is good and we don't see errors as described in this issue. we do see a sporadic cpu/memory spikes but that seems to be related to #1395 - will follow up there. |
Package + Version
@sentry/browser
@sentry/node
raven-js
raven-node
(raven for node)Version:
Description
We're facing issues since
4.5.2
, reverting back to4.5.1
solves the issue. We don't know exactly what is going on, but tried to gather as much information as possible:An endpoint to our Express app report some messages to our Sentry account
With
4.5.2
, our error middleware catches an error and tries to output it is to the user, which results in aCan't set headers after they are sent.
error. It's stack refers to@sentry/node/dist/handlers.js:180:9
:When logging this error to the console, it refers to a TypeError:
TypeError: domain.enter is not a function
:We're also seeing a very strange AssertionError, without any more details about the exceptions (there's no stack):
Reverting to
4.5.1
resolves all these issuesAny help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: