TIL: 'No module named' after an update meant a stale process
My agent said httpx was missing. It was installed. The running process had started before the update and was still on the old environment.
My agent said httpx was missing. It was installed. The running process had started before the update and was still on the old environment.
My IndexNow script read public/sitemap.xml and sent 93 URLs. The live sitemap had 123. The local copy is gitignored, so it only updates when I build.
My MCP server answered 401 even though the API key worked. The header sent the literal text ${VAR} because the variable was only in my shell.
A plain pnpm update would not move a transitive dependency pinned by its parent. A one-line pnpm override did, and GitHub closed the alert.
GNU tar skips an --exclude pattern that ends in a slash and packs the directory anyway. Drop the slash. macOS bsdtar does match it, so test where the backup runs.
Dispatching synthetic blur and change events locks controlled React and MUI inputs. Calling the native property setter and dispatching input only avoids the freeze.
I had three copies of one CLI on my PATH. Homebrew warned that the new one would never run by name, and which -a showed the shadowing.
A TEXT-typed timestamp column compared against a number turns the number into text, so the filter matched rows it should not. Casting the column fixed it.
I edited a pre-push hook in a worktree and nothing changed. Git was running the installed copy from the main repo.
Hundreds of tests failed with React is not defined. The fix was one line in the tsconfig that the component files actually resolve to.
A failed git push piped into tail still exited 0, and the script moved on. set -o pipefail makes the pipeline report the failure.