Background nodes were using tracing without a cutoff value. There are now env vars to control that with default values, just as we do with foreground nodes
Foreground nodes were exiting differently than background nodes. See here. That logic is not relevant anymore, as the opts.shutdown(); is called at the end of every command
Spawned processes are now forked from the main process. This aims to fix the problems of killing processes on docker
Fixes an important issue when recreating nodes. In current develop, when the first node is stopped (e.g. node create --foreground), is left as the default node, so no node could take the default role unless manually set with the node default command. This is now changed so that, when a node checks if it should be the default node, it also takes into account wether the current default node is stopped
Related to the previous, now the default node name used in node create will reuse the stopped node name if possible. That means that running ockam node create --foreground, then exiting, and again ockam node create --foreground will result in using the same node name.
opts.shutdown();is called at the end of every commandnode create --foreground), is left as the default node, so no node could take the default role unless manually set with thenode defaultcommand. This is now changed so that, when a node checks if it should be the default node, it also takes into account wether the current default node is stoppednode createwill reuse the stopped node name if possible. That means that runningockam node create --foreground, then exiting, and againockam node create --foregroundwill result in using the same node name.