concurrency
- 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 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.
- The shutdown grace that never ran
A Go proxy's 5-second shutdown grace was dead code. A real drain and socket activation fixed restarts; KillMode, a WaitGroup and a lock needed fixes too.
- The fixes had the bugs
Seven re-review passes over a Go LLM proxy found 11, 8, 10, 4, 2, 1 and 0 bugs, nearly all in the fixes. Two could have crashed the process.
- The deadlock test can't see a half-held lock
Every model wrote a thread test. Most of them could not fail: with locks taken in id order, opposite-direction transfers serialize on one mutex.
- Zig's defer ends at the closing brace
A local model locked two accounts in the right order, scored 97/100, and lost money. One Zig defer sat inside an if block and unlocked at the brace.