-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
domains: emit uncaughtException when appropriate #3638
Conversation
* given test tests one of these potentially eroneous behaviors that are | ||
* currently accepted as correct. | ||
*/ | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Require common please
5a8cc6b
to
7dd903f
Compare
@misterdjules ... just a quick note: we'll want to land this in |
@jasnell Sounds good. |
Fix node exiting due to an exception being thrown rather than emitting an `'uncaughtException'` event on the process object when no error handler is set on the domain within which an error is thrown and an `'uncaughtException'` event listener is set on the process. Fixes nodejs#3607.
Make the process abort if an error is thrown within a domain with no error handler and `--abort-on-uncaught-exception` is used. If the domain within which the error is thrown has no error handler, but a domain further down the domains stack has one, the process will not abort. Fixes nodejs#3653
13bd31e
to
68ca2b1
Compare
@jbergstroem Thank you for running the tests on this. I think the correct link to the CI results is https://ci.nodejs.org/job/node-test-commit/1040/. Anyway, I needed to run tests again because since then I updated this PR with a new commit. CI running here: https://ci.nodejs.org/job/node-test-pull-request/677/. |
Closing in favor of #3885. |
Fix node exiting due to an exception being thrown rather than emitting
an
'uncaughtException'
event on the process object when no errorhandler is set on the domain within which an error is thrown and an
'uncaughtException'
event listener is set on the process.Fixes #3607.
/cc @nodejs/lts @nodejs/tsc @nodejs/collaborators