Loading…
Reference in a new issue
No description provided.
Delete branch "forced-changes-keep-place"
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?
Bundle A from the 2026-11-18 ticket review: the changes of stream a channel is forced into now keep their place too.
Why. From the app's log for 2026-11-17 07:08Z to 11-18 07:02Z (45 changes of stream, all after the aim fixes):
hls.lshls.st. Every topsurge.st renewal pointed to another stream, and the channel waited for the old address to fail. 2 of these jumped 30 and 94 s.What changes
#169 — a silent stream's standby is kept
kept_segmentsandkept_used, and the change tag's hover says them.#194 — a renewal onto another stream is changed to at once
renewed, wayrenewal). It waits only for a recovery, a tune, an operator's action or another landing.#165 — the buffer step counts
Also in this branch:
9dc1bfaarchivesaim-the-swap(#168, deployed and verified live) into the specs, as its own commit. This change builds on its requirements.Decisions to look at (in the change's
design.md; any may be reversed)Checks
forced-changes-keep-place: valid under--strict, every task ticked.make test: 1522 passed, 1 skipped.npm --prefix frontend test: 290 passed.npm --prefix frontend run buildis clean.make e2e: every leg passed. Its real-page try met a Cloudflare challenge, so it used the fake source.backend/tests/test_forced_changes.pyrun on generated streams. They cover the renewal cases and the silence cases (stay, past the playlist, never, skip ahead, no relation, speaks again, ceiling, nobody watching). With the same-link guard switched off, the another-encode test fails.Live, after the deploy
Closes #169
Closes #194
Closes #165
🤖 Generated with Claude Code