Admin: an action's time left in the buffer starts far too long (18 s shown, 5 s real) #165
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
What happens
The owner pressed Wrong game on a live game (Miami vs. Duke, 2026-11-14 at 15:19:16 EST, two players watching, production at
3a94153). The action worked: acestrims.pages.dev was rejected and givemestreams.cfd reached the players 9.9 s later. But its buffer step opened with far more time left than it took.The action's record, read from
GET /api/channels/{game_id}/operationafter it ended:eta_seconds_at_startwas 18.5. The page shows that figure as "about 18 s left" and measures the bar's buffer part against it (bufferFillinfrontend/src/admin/lanes.ts). So the time left fell about four times faster than a clock. By the history below it most likely read about 18 s, then about 10 s, then about 2 s, then done. Only the finished record was read; the readings in between were not recorded.#163 asked for this display to show "ACCURATE information about what is happening".
Why the figure is too long
Channel._operation_etainbackend/app/channel.pyadds the time until the next release is due to the seconds of every older segment still held ahead of the new stream: one release per segment. Its own comment calls it "the longest it should take".Timeline.releaselets the oldest segment go at once while the buffer holds more than its depth. After a landing the new stream's next segments keep arriving, and each one that puts the buffer over its depth pushes an old segment out early./lanes, 3.5 s bins, 15:19:13 to 15:19:31). When the new stream loaded, two old segments were held (12.4 s, about 6.2 s each) and the next release was due about 6 s later, which makes the 18.5 s. Then releases came 1.9 to 2.0 s apart, where they had been 6.3 to 7.1 s apart, and the new stream's first segment was listed 4.8 s after the load. No filler was listed.Every action that lands a stream takes this path (
Channel._operation_loaded): Swap, Play, Wrong game, and Swap with no standby.The idea
The step shows only what the server knows.
Done when
eta_secondsandeta_seconds_at_startare described as the most it can take, or removed if nothing reads them.admin-pagescenario "The buffer step fills as it goes" (it has "about 9 s left of a 12 s wait" and a quarter-filled bar) and thestream-supervisionscenario for a swap behind one older segment.Rides along
Seen after #161 and not fixed: at page widths near 1,000 px (a window of about 1,310 to 1,345 px) the Links table is 12 px wider than its column, so the Play column is cut at its right edge. In
frontend/src/styles.css,.adm-linkshasflex: 5 1 560pxwhile.adm-table.linkshasmin-width: 640px. Done when the Play column is whole at every width, with the nothing-moves check of #163 still passing.Merged in PR #195 (merge
4d8b2c5), archived infbe6270, live asfbe6270since 2026-11-18 17:54Z.ahead_at_starton the action's record) and how many are left.Not seen live yet: a Swap or Wrong game showing the count.