Raise cluster start timeout to 120 seconds and issue a log warning.
To avoid this stack trace.
(node:32300) UnhandledPromiseRejectionWarning: Error: Cluster start timeout exceeded: 10000ms
at Timeout._onTimeout (C:\Users\Nullivex\WebstormProjects\magic\node_modules\kado\lib\Cluster.js:496:16)
at listOnTimeout (internal/timers.js:551:17)
at processTimers (internal/timers.js:494:7)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:32300) UnhandledPromiseRejectionWarning: Unhandled promise rejection. 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:32300) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Which typically happens right before the program starts.