A Go test that passed 40,000 times, then lost a write under load
Say a client writes a value and gets a success back. Later, the value is gone. It happens once in production, around the time a node restarts, and every test is green. A week later a CI job fails on a test nobody touched. The re-run passes, so someone adds a retry and moves on. Bugs like this need a rare timing, such as a partition during a leader election, or a crash after a write was…
We haven't written up this one. Dev.to has the full story — the link below goes straight to it.
