I notice that each daemon restart re-runs the relevant `experimental_shell_command`each time. We're downloading from network, so this can be expensive. Any pointers on debugging what might've changed in the key?

The quickest stop should be

-ldebug

for 2 runs. I'm pretty sure the whole Process struct is printed out and that contains all the inputs. Not super-convenient, but I think that gives you all the info you need.

I'll try that. Also just checked and my exit code is

0

so we can rule out process failure

mm… a

set

?

does sets iterate in an undefined order?

yes. random per startup.

dict

is deterministic

bummer.