From f6cec2329a700efb847c00850156b01370bb3e66 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 27 Oct 2026 17:08:47 -0700 Subject: [PATCH 1/3] chore(quest): claim quest/m0/backport-frame-start.md Quest-Claim: 0d12bd8d337eb6c6 From 076756835e15ebe2287dae7e4fdf8cee46de3e63 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 27 Oct 2026 17:17:27 -0700 Subject: [PATCH 2/3] chore(quest): track the prepared frame-start backport Co-Authored-By: GPT-6 --- quest/m0/backport-frame-start.md | 33 ++++++++++++++++---------------- 1 file changed, 17 insertions(+), 16 deletions(-) diff --git a/quest/m0/backport-frame-start.md b/quest/m0/backport-frame-start.md index fbfed094614..15b79d55aee 100644 --- a/quest/m0/backport-frame-start.md +++ b/quest/m0/backport-frame-start.md @@ -1,25 +1,26 @@ -# [S] Backport the frame-start refusal to release +# [S] Merge and publish the frame-start refusal backport ## Goal -`@moq/net` on `release` refuses a lite group stream that starts at a nonzero -frame instead of silently numbering its frames from zero, and publishes a -patch release. +[moq-dev/moq#6967](https://github.com/moq-dev/moq/pull/6967) merges to +`release`, and a patch of `@moq/net` containing it publishes. The published +reader refuses a lite group stream starting at a nonzero frame rather than +silently numbering its frames from zero. ## Plan -Decided 2026-10-27 (maintainer): one PR against `release` per backport, in -m0, JS only. From -[moq-dev/moq#6922](https://github.com/moq-dev/moq/pull/6922), which makes -main honour a frame start. Release's Rust half does not apply (it lacks the -fill and group content model), and the #6903 and #6919 fixes are not -backported: #6919's `--stitch` is main-only, and #6903 would be a rewrite -against release's older watch API for a playback glitch. +The release implementation above ports the refusal from +[moq-dev/moq#6395](https://github.com/moq-dev/moq/pull/6395), with a regression +that verifies refusal and that no misnumbered group reaches the consumer. +Both strict release CI gates pass. -As of 6ce67943f7, release's `js/net/src/lite/subscriber.ts` creates -`new netGroup.Producer(group.sequence)` and never reads the frame start, so -a mid-group start misnumbers frames, while release's Rust publisher can -send one. Refuse a nonzero start as main did before #6922 (the refusal -added in [moq-dev/moq#6395](https://github.com/moq-dev/moq/pull/6395)). +Decided 2026-10-27 (maintainer): PR creation only in this session; merging +and publication remain for a later authorized session. No package version +was bumped. Delete this quest and its links after the release PR merges and +its patch publishes. + +The Rust changes from +[moq-dev/moq#6922](https://github.com/moq-dev/moq/pull/6922) depend on main's +newer group model and remain excluded from this JS-only backport. Public API: none. Wire: none; refuses a stream it misread before. From efdd0653a1371d2d6f6e148511953e993df4c1b7 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 27 Oct 2026 23:31:07 -0700 Subject: [PATCH 3/3] chore(quest): finish the frame-start release backport The backport merged to release and @moq/net 0.4.7 published it. Co-Authored-By: Claude Opus 5.5 --- quest/m0/README.md | 1 - quest/m0/backport-frame-start.md | 26 -------------------------- 2 files changed, 27 deletions(-) delete mode 100644 quest/m0/backport-frame-start.md diff --git a/quest/m0/README.md b/quest/m0/README.md index 8357acee985..324018f548a 100644 --- a/quest/m0/README.md +++ b/quest/m0/README.md @@ -25,7 +25,6 @@ edge, which embeds moq-relay; it moved there on 2026-09-28. - [Backport IETF close codes](/quest/m0/backport-ietf-close-codes.md) - `@moq/net` on `release` closes moq-transport sessions with the right error for three hostile cases - [Backport @moq/flate bounds](/quest/m0/backport-flate-budget.md) - `@moq/flate` on `release` stops inflating past its cap and stops pinning pako scratch - [Backport MKV, FLV, and VP9 import fixes](/quest/m0/backport-mux-import.md) - moq-mux on `release` refuses malformed imports instead of wrapping, panicking, or dropping tracks -- [Backport the frame-start refusal](/quest/m0/backport-frame-start.md) - `@moq/net` on `release` refuses a nonzero lite frame start instead of misnumbering frames - [Smoke tests the released packages](/quest/m0/smoke-released.md) - smoke clients call only released APIs and every red cell is fixed, so Smoke passes on main - [CI cost and latency](/quest/m0/ci/README.md) - cloud CI runs only in a batched merge gate as one `just ci` pass per batch, expensive checks run nightly and gate `release`, caches move to R2, and runners are chosen last - [More tests under load](/quest/m0/test-flakes-2/README.md) - load-only and queue failures, one quest per flake, fixed at the cause, since each one fails a whole batch diff --git a/quest/m0/backport-frame-start.md b/quest/m0/backport-frame-start.md deleted file mode 100644 index 15b79d55aee..00000000000 --- a/quest/m0/backport-frame-start.md +++ /dev/null @@ -1,26 +0,0 @@ -# [S] Merge and publish the frame-start refusal backport - -## Goal - -[moq-dev/moq#6967](https://github.com/moq-dev/moq/pull/6967) merges to -`release`, and a patch of `@moq/net` containing it publishes. The published -reader refuses a lite group stream starting at a nonzero frame rather than -silently numbering its frames from zero. - -## Plan - -The release implementation above ports the refusal from -[moq-dev/moq#6395](https://github.com/moq-dev/moq/pull/6395), with a regression -that verifies refusal and that no misnumbered group reaches the consumer. -Both strict release CI gates pass. - -Decided 2026-10-27 (maintainer): PR creation only in this session; merging -and publication remain for a later authorized session. No package version -was bumped. Delete this quest and its links after the release PR merges and -its patch publishes. - -The Rust changes from -[moq-dev/moq#6922](https://github.com/moq-dev/moq/pull/6922) depend on main's -newer group model and remain excluded from this JS-only backport. - -Public API: none. Wire: none; refuses a stream it misread before.