You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
observe(hls): log first playlist push + first stream.m3u8 per camera
The previous regex fix (6c83fea) didn't resolve the Pi playback issue
— segments keep pushing but the player still spins after 1200+
segments. Guessing further burns time; we need ground truth from
Fly logs.
Add two one-shot INFO logs that fire exactly once per camera id per
backend restart:
- ``hls: first playlist push`` — on POST /playlist, captures raw
size, rewritten size, first segment URI, and resolved codecs.
Tells us instantly whether CloudNode is reaching the endpoint at
all, and if so what shape its playlist is.
- ``hls: first stream.m3u8 HIT/MISS`` — on GET /stream.m3u8,
distinguishes between "cache hit and served" vs "CloudNode never
pushed — 404 back to browser". A MISS with segment cache non-empty
is the smoking gun for "segments arriving but playlist isn't".
Gated behind a ``set[str]`` flag so we log once and shut up — with
hls.js retrying at 400ms and CloudNode pushing at 1 Hz, unmuted INFO
logs would flood. ``cleanup_camera_cache`` clears the flag so a
reconnecting camera re-announces.
No behavior change — only telemetry.
0 commit comments