claude
dd699b706f
Three ways a mavpoll process died or lied after start: - -interval 0 panicked time.NewTicker on the first tick. - -timeout 0 is 'no deadline' to http.Client, so one wedged source stalls every source behind it forever. - -wg-cmd '' indexed field 0 of an empty slice in pollWg. All three are now refused in run(), where the operator reads the message, and pollWg guards its own command as well. A body that hits maxBodyBytes was silently truncated. A cut kuma page parses cleanly up to the cut and every monitor past it looks deleted, so the poller would write 'unknown' over live services and the down-rule would go quiet. Read one byte past the cap and refuse. wg's stderr was dropped by Output(), leaving 'exit status 1' in the log where the real cause is a missing CAP_NET_ADMIN or a bad interface.