-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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
Documentation: process event uncaughtException pointing to deprecated module #2055
Labels
doc
Issues and PRs related to the documentations.
Comments
Yes, definitely. I think even leaving the error in place without a solution is a good idea. |
wouldn't one want to process.exit gracefully |
benjamingr
added a commit
to benjamingr/io.js
that referenced
this issue
Jul 2, 2015
This PR closes nodejs#2055 by removing the suggestion to use domains for exception handling. Additionally clarify `unhandledException` a bit. PR-URL: nodejs#2056 Reviewed-By: Trev Norris <trev.norris@gmail.com> Reviewed-By: Chris Dickinson <chris@neversaw.us>
Fixed by 0f09b8d. |
Thanks :) |
mscdex
pushed a commit
to mscdex/io.js
that referenced
this issue
Jul 9, 2015
Remove the suggestion to use domains for exception handling. Add clarity to "unhandledException". Fixes: nodejs#2055 PR-URL: nodejs#2056 Reviewed-By: Trev Norris <trev.norris@gmail.com> Reviewed-By: Chris Dickinson <chris@neversaw.us>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On the Process event
'uncaughtException'
documentation, you are pointed to use domains instead for exception handling.Given that the domain module is pending deprecation, an alternative solution should be documented.
The text was updated successfully, but these errors were encountered: