assertion failing is: // (in tokio code, in `src/time/driver/entry.rs`) debug_assert!(cur_state < STATE_MIN_VALUE); Huh, a debug_assert!. That means that in production… $ RUST_BACKTRACE=1 cargo run --quiet --release (program never outputs anything, never exits either) Hah. I guess they’re not fucking around about the “undefined

need to reorganize all my manifests carefully. But I was already down, and it’s been a shit month, so, I decided to treat myself. The deploy-manifests script, even in its latest incarnation, still blows. A better version would merge all resources in a single YAML file, and compare against what the control node already has, requiring --fuck-me-up

is still a warning - just something we should look at when we get a chance, but not a showstopper. (Unless we slap #![deny(unreachable_code)] at the start of our main.rs, the equivalent of passing -Werror=something to gcc/clang). Fuck around now, find out… when? Let’s change our sample a little bit. Say we remove the definition of bar entirely