From 4cb67e778b58e23be21a1600b45167167d6259e1 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 22 Oct 2026 09:00:06 -0700 Subject: [PATCH] quest: complete release-fixed-delay The fix landed on release in #6217. Co-Authored-By: Claude Opus 5.5 --- quest/m0/README.md | 1 - quest/m0/release-fixed-delay.md | 24 ------------------------ 2 files changed, 25 deletions(-) delete mode 100644 quest/m0/release-fixed-delay.md diff --git a/quest/m0/README.md b/quest/m0/README.md index 7daf1289a1b..d589a7aa652 100644 --- a/quest/m0/README.md +++ b/quest/m0/README.md @@ -44,7 +44,6 @@ Each lands its fixes in its own PR and plans only what needs a decision. - [web-transport-proto 0.6.3](/quest/m0/web-transport-proto-0.6.3.md) - `main` and `release` lock the upstream release that bounds decoded CONNECT headers, so a peer can't make a relay hold megabytes per session before auth - [qmux 0.5.3](/quest/m0/qmux-0.5.3.md) - crates.io publishes qmux 0.5.3 with the builder session config the release backport of #5609 needs - [Release shutdown backport](/quest/m0/ffi-shutdown-backport.md) - `release` publishes a non-breaking moq-ffi with an async `drain()` and qmux sessions on the QUIC stream limit -- [Release fixed delay](/quest/m0/release-fixed-delay.md) - a fixed latency on `release`, which moq.dev runs, ignores the catalog's jitter and delay as `main` already does - [Release resubscribe hang](/quest/m0/release-resubscribe-hang.md) - a moq-lite-06 subscription that closes and reopens on `release` is proven to reach the relay, or the hang is fixed and backported - [CI cost and latency](/quest/m0/ci/README.md) - cloud CI runs only in the merge queue as one `just ci` pass, expensive checks run nightly and gate `release`, caches move to R2, and runners are chosen last - [Simplification audit](/quest/m0/audit-simplify.md) - overbuilt code and APIs are collapsed, merged, or narrowed into a net simpler whole diff --git a/quest/m0/release-fixed-delay.md b/quest/m0/release-fixed-delay.md deleted file mode 100644 index 56e49499968..00000000000 --- a/quest/m0/release-fixed-delay.md +++ /dev/null @@ -1,24 +0,0 @@ -# [XS] A fixed latency on release ignores the catalog jitter and delay - -## Goal - -On `release`, which `moq.dev` runs, a viewer who picks a fixed latency -(100 ms, 250 ms, ...) plays at that delay. Today `Sync.#runDelay` -(`js/watch/src/sync.ts` on `release`) adds every rendition's catalog -`delay + jitter` on top of the fixed value, so a publisher whose estimates -ratchet up drags a "100 ms" viewer tens of seconds behind; a user reported a -42 s total buffer with 100 ms selected. - -## Plan - -`main` already behaves this way since -[#4162](https://github.com/moq-dev/moq/pull/4162), but that change is a -breaking `@moq/watch` rework that won't be backported. Port only the behavior: -when the configured delay is a number, the output delay is that number; -"auto" and "instant" are unchanged. - -- The PR targets `release` directly, with no `main` change, and keeps the - published API so it ships as a patch (see `CONTRIBUTING.md`). -- Add a regression test in `js/watch/src/sync.test.ts` on `release`: a - registered rendition jitter does not raise a fixed delay. -- The fix reaches `moq.dev` with the next release deploy.