diff --git a/quest/m0/README.md b/quest/m0/README.md index ece91eafa74..5b220fd9599 100644 --- a/quest/m0/README.md +++ b/quest/m0/README.md @@ -30,7 +30,6 @@ edge, which embeds moq-relay; it moved there on 2026-09-28. - [Interop and Video pass on main](/quest/m0/interop-green/README.md) - the scheduled Interop and Video workflows pass, so red means a new break - [Publish the release line's drain() wrappers](/quest/m0/ffi-shutdown-backport.md) - Dart `moq` 0.1.1 reaches pub.dev from `release` - [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 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 - [CI cost and latency](/quest/m0/ci/README.md) - cloud CI runs only in GitHub's merge queue, one tested entry at a time, 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 drops a queued PR - [Backport the relay and auth hardening to release](/quest/m0/backport-release-hardening.md) - `release`'s relay refuses dot-segment paths, serves its HTTP routes with main's response hardening, and withdraws advertisements a peer starves of send credit; its auth client refuses redirects diff --git a/quest/m0/backport-fill-head-race.md b/quest/m0/backport-fill-head-race.md deleted file mode 100644 index 3105257ede8..00000000000 --- a/quest/m0/backport-fill-head-race.md +++ /dev/null @@ -1,44 +0,0 @@ -# [S] Ship the joined-head FETCH race backport - -## Goal - -The `release` relay no longer races its subscription's joining head with a -cache-miss FETCH, and the fix reaches users in a `moq-net` patch release. -Public API and wire stay unchanged. - -## Plan - -[moq-dev/moq#7135](https://github.com/moq-dev/moq/pull/7135) merged on `main`. -The relay fix is hand-ported in [moq-dev/moq#7680](https://github.com/moq-dev/moq/pull/7680), targeting `release`. - -The race reproduced on `release`: both joined-head miss tests sent an extra -FETCH while the subscription's own fill was still outstanding. The older-history -control fetched immediately. The port preserves those cases and covers reader -cancellation and track abort using release's paused-time harness. - -Decided 2026-10-30 and reaffirmed 2026-11-01 (maintainer): port only the relay -fix. Release's JS publisher refuses every FETCH, so the old publisher timestamp -bug cannot happen there. The settled main PR also carries only the relay fix. - -The port uses release's existing per-group requests and joining `Fill`; it -imports none of main's range-fill or subscription-widening machinery. The -joined group waits for its own head or a settled fill, the cache answers a head -that arrives, and a remaining miss still FETCHes. Older history does not wait. - -Local review also exposed a pending miss no longer being polled during the -PUBLISH_DONE grace. The backport adds that poll and a paused-time reproduction. -[moq-dev/moq#7903](https://github.com/moq-dev/moq/pull/7903) landed the same -correction on main first (merged 2026-11-05), following the main-first -backport rule. Its other -change, driving a lingering copy's fetches while a resumed SUBSCRIBE is set up, -has no `release` counterpart: release creates its fetch set after SUBSCRIBE_OK -and never lingers. - -After the backport lands, use the existing patch-release process. Package -version bumps, tags, and publication are separate from this implementation -attempt. Verify that the published `moq-net` patch contains the backport, then -remove this quest and its links. - -## Waiting - -- Maintainer: review and merge [moq-dev/moq#7680](https://github.com/moq-dev/moq/pull/7680) after the release checks pass, then publish the `moq-net` patch through the normal release process; verify its source contains the joined-head wait. Agents never merge into `release`, bump versions, tag, or publish, so these steps stay manual.