> Bash scripts did not have set -x so continued to run even after the stop command had failed.

I hope that's a typo in transcription and they actually used `set -e` to fix (and maybe `set -o pipefail`), `set -x` does something entirely different.

alas poor yorick

I’ve been through similar scenarios and they went down like this. Scrambling, making notes about things that should have been done while putting full understanding beside to fight the fire. I used to think there was a better way, now I’m convinced there is but it would take too much time across the stack and still go down anyways because you can’t control everything all the time forever.

Super transparent at least

Even that took 10s to load for me, haha.

    18h45 
    Yorick is doing the vacuuming. Vacuuming is not doing it’s thing. Why….
    
    18h48 
    Still not vacuuming.
    
    18h50 
    Yorick: still not sure why it’s not vacuuming.    
    We need a roomba.

I love them :)