Skip to content
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.

Sign up for GitHub

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

Jump to bottom

process: add --unhandled-rejections flag #26599

Closed
wants to merge 2 commits into from
Closed

process: add --unhandled-rejections flag #26599

wants to merge 2 commits into from

Commits on Apr 10, 2019

  1. src: print error before aborting 

    In case of fatal errors, first print the error before aborting in
case the process should abort on uncaught exceptions.
    @BridgeAR
    BridgeAR committed Apr 10, 2019
    Configuration menu
    Copy the full SHA
    43a6164 View commit details
    Browse the repository at this point in the history

  2. process: add --unhandled-rejections flag 

    This adds a flag to define the default behavior for unhandled
rejections. Three modes exist: `none`, `warn` and `strict`. The first
is going to silence all unhandled rejection warnings. The second
behaves identical to the current default with the excetion that no
deprecation warning will be printed and the last is going to throw
an error for each unhandled rejection, just as regular exceptions do.
It is possible to intercept those with the `uncaughtException` hook
as with all other exceptions as well.

This PR has no influence on the existing `unhandledRejection` hook.
If that is used, it will continue to function as before.
    @BridgeAR
    BridgeAR committed Apr 10, 2019
    Configuration menu
    Copy the full SHA
    14914bf View commit details
    Browse the repository at this point in the history