3 ms·
Gitlab working document https://docs.google.com/document/d/1WmOMKq63Rap2wfQ-yy7sHyocFvmbJgIt1UIj2xEXEco/preview https://docs.google.com/document/d/1WmOMKq63Rap2
by dpcx 8y ago
Gitlab working document https://docs.google.com/document/d/1WmOMKq63Rap2wfQ-yy7sHyocFvmbJgIt1UIj2xEXEco/preview https://docs.google.com/document/d/1WmOMKq63Rap2wfQ-yy7sHyoc...
- haskellandchill 8y agoI’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.
- Moter8 8y agoEven that took 10s to load for me, haha.
- sbhn 8y agoalas poor yorick
- rhacker 8y agoSuper transparent at least
- lunixbochs 8y ago> 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.
- YorickPeterse 8y agoYes that's a typo, it should have been `set -e`
- batat 8y ago18h45 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 :)