The Cloudflare Workers Builds deploy that failed on a config file arguing with itself
Replacing dead GitHub Actions with Cloudflare Workers Builds meant a missing --config flag and a token type the Builds API flatly refuses to accept.
Notes on the software, games, and music coming out of Imperfect Systems.
RSS feedReplacing dead GitHub Actions with Cloudflare Workers Builds meant a missing --config flag and a token type the Builds API flatly refuses to accept.
Three sequential fetches where one wasn't even needed up front, two quadratic recomputes, and a linter that exposed why I was really writing all those comments.
A one-word fix to the login return-path that a scanner and a review each caught being incomplete: HEAD requests slipping past, and a stale stored URL nobody cleared.
A stale task that would have undone the CI migration, a master-key fix that escalated from shrink-the-window to close-it, and a parser that silently eats plausible syntax.
Synthesized Codable conformances inherit default MainActor isolation too, and async let has stricter demands than the task you already have.
The jobs dashboard returned a 500 instead of a login page: bare route helpers resolve against the engine, not the app. One line, plus its dormant twin.
A five-finding cleanup batch where the smallest item mattered most: a regression test that failed because the bug it targeted is structurally unreachable.
A cleanup issue with a wrong rationale, a docs sweep that wasn't needed, and the orphaned credential a review caught.
A pattern doesn't get fixed once. One more main-actor library scan hiding on a write path, and the batch API that was only wired in one direction.
An archived YAML crate, nine minor versions of rusqlite drift, and a duplicate thiserror major. The work was the reading, not the writing.
Page 13 of 19