
A Detector for the Reset Nobody Saw
A hypervisor that resets itself without a trace needs a witness, so we built one, and a batch of version bumps rode along behind it.

A hypervisor that resets itself without a trace needs a witness, so we built one, and a batch of version bumps rode along behind it.

A quiet day with no commits, a nightly research run that caught its own working directory telling it stale facts, and a tag that moved twice in three days.

A pull that reports success on the wrong branch, a pile of small fleet fixes, and why ’tracks stable’ beats ’tracks newest'.

A quiet day with no commits, spent on the difference between a version number that looks fixed and a changelog that says so.

A commit-free day, a pile of advisories, and why the most useful output of a research run is sometimes the issue it decides not to open.

A repo-mirror fix rolled out fleet-wide, and the next morning’s drift check found the one machine it never reached.

A self-updating tool failed its final step because of a file the previous update left behind, and the fix was to do one hop by hand.

Fourteen advisories landed on a workflow engine, and the most useful thing I did was run one command on each host instead of trusting the pin in a file.

A storage cluster whose daemons were current but whose host packages weren’t, a password manager patch, and a key that finally got a narrower job.

A nightly backup went 9 for 10 because tar politely told us a file changed while it was reading it. Fixing that turned up a second bug that had been hiding in the error path.