go
- The UPS said 2 minutes at 95 %
A UPS monitor took the minimum of three runtime estimates and raised low battery at 95 %. One of them was the station's time to full charge.
- The DJI went silent for four hours
A DJI Power 2000 stopped advertising over Bluetooth while the monitor served its last reading as live. Then the observer revived its own four-hour-old state.
- My drift check said 0 differences. It checked 4 arrays.
My Go checker read a bash model config without running it and said 0 differences. It compared 4 arrays. The fail-closed rewrite found a missing output cap.
- In opencode 1.19.5, my workaround protected nothing
I renamed model keys so opencode wouldn't force top_p on my local models. In 1.19.5 it matches the id I sent anyway, and the qwen rule is gone.
- The race detector saw my requests in order
A mutant removed a lock in my Go proxy and survived -race. The test sent its requests one after another, and that order hid the unlocked read.
- The poller that wasn't stuck
One timestamp an hour older than its process sent me after a hung Go poller. A goroutine dump killed that theory; a local-time RTC after DST explained it.
- The config said 32k. The engine still ran 64k.
Adding SIGHUP reload to a Go LLM proxy: a whitelist of three settings, a model list that runs ahead of the engines, and a refresh that finished last.
- My isolation guard checked itself
A guard meant to prove my Go tests couldn't reach the live proxy compared a path with the env var it guarded, and passed on any shell that had set it.
- The mutant was killed after it switched a real GPU
A hand-written mutant made my Go CLI skip -proxy. Its test failed on cue, after a real model load that then kept a benchmark off a GPU for almost half an hour.
- The lock map deleted a mutex someone was waiting on
A Go transfer by Flash-Next Q2_0 scored 100 and passed 6 of 6 failure-path tests. One cleanup line let a retried key move the money twice.