Exit 0 is the strongest claim a program can make
The job told me, very politely, that it hadn't done its job, and then exited 0. Two questions were enough to undo the spec written to fix it.
Tags
5 pages
Error-Handling
Merged in five days, open in seven hundred
Leaving a healthy dependency: cockroachdb/errors predates Go 1.20, so its Join hides the aggregate and everything below it goes missing.
The afternoon the agent earned its keep
Adding stream-copy remux to a WebAssembly FFmpeg build, where writing Matroska hung forever and the identical MP4 path did not.
Errors without an error handler
Go funnels errors through a handler. In Rust, diagnostics carry their own code and help and propagate on their own, so the funnel disappears.
Errors that tell the user what to do next
Recovery advice belongs in a structured error hint, not buried in the message string. One error handler then decides how to show it.
