You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node.js process should exit when unhandled promise rejection occurs
Current Behavior
Node.js process does not exit when unhandled promise rejection occurs
Possible Solution
Node.js process should exit because it's the default behavior after node.js 15, we depend on this behavior to restart and retry to finish the application startup process.
Steps to Reproduce
During the startup process, after an unhandled rejection is thrown, the node.js process does not exit.
Additional Information
The text was updated successfully, but these errors were encountered:
% docker run --rm node:18.19.0-alpine3.17 -e 'Promise.reject("test")'
node:internal/process/promises:288
triggerUncaughtException(err, true /* fromPromise */);
^
[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "test".] {
code: 'ERR_UNHANDLED_REJECTION'
}
Node.js v18.19.0
% echo $?
1
Perhaps this has to do with how your container is run.
Environment
Expected Behavior
Node.js process should exit when unhandled promise rejection occurs
Current Behavior
Node.js process does not exit when unhandled promise rejection occurs
Possible Solution
Node.js process should exit because it's the default behavior after node.js 15, we depend on this behavior to restart and retry to finish the application startup process.
Steps to Reproduce
During the startup process, after an unhandled rejection is thrown, the node.js process does not exit.
Additional Information
The text was updated successfully, but these errors were encountered: