Currently the daemon shuts itself down on an uncaught exception or unhandled rejection. That makes sense for ensuring a working state (manager processes can detect the close and restart) but when I've got the daemon embedded in Beaker, it causes problems because unhandled rejections are sometimes allowed.
Could we add a flag to disable that or move the behavior outside of the core code or something?
Currently the daemon shuts itself down on an uncaught exception or unhandled rejection. That makes sense for ensuring a working state (manager processes can detect the close and restart) but when I've got the daemon embedded in Beaker, it causes problems because unhandled rejections are sometimes allowed.
Could we add a flag to disable that or move the behavior outside of the core code or something?