From 5999d8cd442d0beee5f4293f114991624dec03e7 Mon Sep 17 00:00:00 2001 From: Richard Hansen Date: Tue, 9 Feb 2021 00:04:20 -0500 Subject: [PATCH] server: Only pass `err` arg to `exports.exit()` The `uncaughtException` event handlers are passed two arguments: error and "origin". The `exports.exit()` argument doesn't expect a second argument. --- src/node/server.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/node/server.js b/src/node/server.js index 453860a0a..c05cba17b 100755 --- a/src/node/server.js +++ b/src/node/server.js @@ -108,7 +108,7 @@ exports.start = async () => { stats.gauge('memoryUsage', () => process.memoryUsage().rss); stats.gauge('memoryUsageHeap', () => process.memoryUsage().heapUsed); - process.on('uncaughtException', exports.exit); + process.on('uncaughtException', (err) => exports.exit(err)); // As of v14, Node.js does not exit when there is an unhandled Promise rejection. Convert an // unhandled rejection into an uncaught exception, which does cause Node.js to exit. process.on('unhandledRejection', (err) => { throw err; });