A burst no longer stops the buffer's clock, and the card counts long waits #160
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/buffer-clock-after-burst"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
Raptors vs. Celtics on 2026-11-12 (givemestreams.cfd, the Shield through Emby's direct stream) froze or skipped briefly now and then while the Admin card said Healthy and Steady.
Measured 02:25–02:36Z:
Cause
Timeline._releaseadded a segment length to the next due time for every release, including one made only because the buffer was over its depth. Nothing took that back. After the first burst the clock was due further ahead for good (up to the buffer's depth), so it never fired, and every release waited for the source's next segment: one in, one out. A full buffer smoothed nothing.Nothing counted it either: a release is only marked late when the clock makes it, the no-new-segment rule starts at 16 s, and the served rate averages a wait and its burst back to real time.
What changes
test_a_bursty_source_is_released_evenly, which fails on the old code with 10.0 s).served.long_waitsandserved.longest_wait.stream-supervision, one inadmin-page.Things to know
Testing
make test: 1261 passed, 1 skipped. Frontend: 265 passed, build clean. Not yet checked against a live game; the check after deploy is to sample a playing channel's playlist beside/api/channelsand see the waits gone.🤖 Generated with Claude Code