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
Currently, when Sandbox is ordered to shut down, it does so immediately. This is a pretty nice user experience, as it keeps things moving super fast, especially in tests.
However, sometimes a Lambda may still be executing. Sandbox will shut down, and the spawned process, now without a parent, may start outputting red herring errors to the console.
I'm thinking an option (or change of defaults) to wrap up executions before shutting down might be helpful. Some ideas:
Module
// Immediately terminatesawaitsandbox.end()// Wait for all Lambdas to terminate; this could in theory delay shutdown by up to 15 minutesawaitsandbox.end({clean: true})// Same as above, but force termination after 5 seconds?awaitsandbox.end({clean: true,forceShutdown: 5000})
CLI
# ctrl-c → Immediately terminates# ctrl-c
$ There appear to be 3 Lambda processes still running, would you like to waitfor them to finish?> Wait for processes to finish
Terminate immediately
The text was updated successfully, but these errors were encountered:
Currently, when Sandbox is ordered to shut down, it does so immediately. This is a pretty nice user experience, as it keeps things moving super fast, especially in tests.
However, sometimes a Lambda may still be executing. Sandbox will shut down, and the spawned process, now without a parent, may start outputting red herring errors to the console.
I'm thinking an option (or change of defaults) to wrap up executions before shutting down might be helpful. Some ideas:
Module
CLI
The text was updated successfully, but these errors were encountered: