diff --git a/quest/m0/README.md b/quest/m0/README.md index d9632cea647..b720e0832bc 100644 --- a/quest/m0/README.md +++ b/quest/m0/README.md @@ -29,7 +29,6 @@ edge, which embeds moq-relay; it moved there on 2026-09-28. - [Backport audio groupDuration](/quest/m0/backport-audio-group-duration.md) - `@moq/publish` 0.5.4 on `release` can pack several Opus frames per group, making Cloudflare's relay drop audio less often - [Backport the SETUP-path and iroh-key fixes](/quest/m0/backport-security-fixes.md) - `release` refuses a conflicting SETUP Path and keeps persisted iroh keys private, in one patch release - [Backport the joined-head FETCH race fix](/quest/m0/backport-fill-head-race.md) - a `release` relay stops FETCHing a group head its own SUBSCRIBE is bringing, which left live readers hanging -- [Release resumes owed groups or proves it doesn't need to](/quest/m0/backport-resume-owed-groups.md) - after main's resume fix, reproduce its cases on `release`, then backport or delete - [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 - [A waiter's record limit changes no behavior](/quest/m0/kio-waiter-records.md) - two moq-net tests stop failing when kio's waiters remember 16 lists, and the limit becomes a tuning knob worth 3.9% per delivered group diff --git a/quest/m0/backport-resume-owed-groups.md b/quest/m0/backport-resume-owed-groups.md deleted file mode 100644 index 41b2aa16757..00000000000 --- a/quest/m0/backport-resume-owed-groups.md +++ /dev/null @@ -1,35 +0,0 @@ -# [S] Release resumes owed groups or proves it doesn't need to - -## Goal - -A `release` relay's resumed read gets every owed group or a drop for it, -never a hang, if `release` has the hang. Otherwise, this quest records the -evidence that `release` isn't exposed and is deleted. - -## Plan - -Decided 2026-11-03 (maintainer, /quest-plan of the follow-ups from -[moq-dev/moq#7708](https://github.com/moq-dev/moq/pull/7708)): milestone m0, -beside the other backports. It started once #7708, the resume fix on main -that this ports, merged. - -- Exposure is unproven. `origin/release` (moq-net 0.3.19 at `acf91a00b9`) - has no `live_floor`, `judge`, or `Misses`. The shared live floor that - #7708 fixes arrived with - [moq-dev/moq#4741](https://github.com/moq-dev/moq/pull/4741), which is not - on `release`. `release` does have `resume.rs`, so - the symptom may still come through another path. - `release` also speaks draft 22 (`rs/moq-net/src/ietf/version.rs`), so - check drafts 14 to 22. -- Reproduce first. Port #7708's regression tests (the cache-loss case and - the bounded resumes) onto `release`'s older cache model and run them - there. If none fails, delete this quest and record the run in the PR. -- If one fails, fix it on `release` with the smallest change that matches - main's contract. Expect a hand-port, not a cherry-pick, since the cache - models differ. Then cut a patch release under the release line's usual - rules. Bump the version by hand at the semver level the change needs. -- Keep it separate from [the joined-head FETCH backport](/quest/m0/backport-fill-head-race.md). - #7708 says the PUBLISH_DONE grace correction tracked there is a separate - fix. - -Public API: none expected. Wire: none. diff --git a/quest/m2/release/cut.md b/quest/m2/release/cut.md index dce91cba871..8da4e5a0fa4 100644 --- a/quest/m2/release/cut.md +++ b/quest/m2/release/cut.md @@ -33,6 +33,11 @@ MKV buffering fix to release, which stays exposed until then. Backport it to (maintainer, 2026-11-03). A blanket size cap would refuse supported inputs and miss the decoder's captured children, as [moq-dev/moq#7718](https://github.com/moq-dev/moq/pull/7718) measured. +It likewise ships [moq-dev/moq#7708](https://github.com/moq-dev/moq/pull/7708)'s +resumed-history fix: release (moq-net 0.3.20) loses a resumed IETF reader's +cached groups on drafts 14 to 22. ✅ No backport (maintainer, 2026-11-04; +[moq-dev/moq#7815](https://github.com/moq-dev/moq/pull/7815)), so check +both fixes reach release. Recurs once per major release (decided 2026-10-19). The PR that finishes the cut shifts the milestones up, as the root [questline](/quest/README.md)