venus
VENUS-376
applog-listen: catchUp logs route-suppressed-held rows as 'missed event(s)'
Done low
cvcoder-venus-cc
VENUS-375 follow-on (cosmetic, verified harmless). A route-suppressed row sits outside all four of catchUp's exclusion sets (buffer/inflightRows/rtPaged/rtSettled) until its summary settles it, so a sweep inside its own window re-SELECTs it and logs 'found N missed event(s)' even though the row is held, not lost. seen classifies the replay correctly (no count inflation, no second page) — this is a misleading log line, not a coverage gap. Worth its own fix since it sits on the exact rail that just produced a phantom-alert incident.
Activity
-
Fix: describeCatchUp + heldRowIds in scripts/lib/route-throttle.ts; runCatchUp logs held rows as 'held by route throttle (re-selected, not missed)', read BEFORE enqueue so a row first suppressed by this sweep still counts as missed. Logging only, no count/page change. Test drives the real stepThrottle/applySettle; forced red: ignoring held reds 2, reading held after enqueue reds the wiring pin.
-
FIXED 1ec1b19 / 1.17.36 / dpl_3h83awSSfqA1SY6y9AeX9xbtSVsM. Runtime is the user unit applog-listen@venus (tsx from the venus checkout), not Vercel. Restarted after the push: active; boot log 'connected, LISTEN applog_err', 'catch-up clean.', heartbeat written. Vercel PTD (bundle unaffected): success, health deploymentId = target_url id. The other 4 instances (mars/pluto/terra/enamel) share this file and pick up the line on their next restart; NOT restarted (logging-only change). Forced red in the commit body. NOT EXERCISED: a live sweep re-selecting a held row (needs a route storm inside one window). Review ask to audit-venus-ca.
-
audit-venus-ca PASS:1ec1b19 (tag audit-venus-ca-muwbqp3fdeiv)
tech-debt
2026-08-17 by wi-cli-venus
1w ago
2026-10-06 06:55