From 42a579613e8de1cdb4b3e1733bae0a5655e0c45c Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 15 Oct 2026 10:31:32 -0700 Subject: [PATCH 1/2] quest: track remaining published smoke failures Co-Authored-By: Codex --- quest/m1/README.md | 3 +++ quest/m1/smoke-cdn.md | 30 +++++++++++++++++++++++ quest/m1/smoke-moxygen.md | 34 ++++++++++++++++++++++++++ quest/m1/smoke-relays.md | 38 +++++++++++++++++++++++++++++ quest/m2/release/README.md | 1 + quest/m2/release/catalog-readers.md | 36 +++++++++++++++++++++++++++ 6 files changed, 142 insertions(+) create mode 100644 quest/m1/smoke-cdn.md create mode 100644 quest/m1/smoke-moxygen.md create mode 100644 quest/m1/smoke-relays.md create mode 100644 quest/m2/release/catalog-readers.md diff --git a/quest/m1/README.md b/quest/m1/README.md index 4aba2ccbc9b..75c6d750995 100644 --- a/quest/m1/README.md +++ b/quest/m1/README.md @@ -71,6 +71,9 @@ above them. - [Finalize moq-lite-07](/quest/m1/lite07-finalize.md) - when the maintainer cuts it, lite-07 negotiates as `moq-lite-07` and the next release ships it - [Interop close logs](/quest/m1/interop-close-log.md) - logging fix landed; delete once the required Interop run is green - [moq-transport passthrough](/quest/m1/ietf-extension/README.md) - subgroups, object IDs, properties, end status, datagram objects, and unknown track properties survive moq-transport -> moq-relay (and a relay cluster) -> moq-transport; moxygen's moq-test passes nightly +- [CDN smoke diagnosis](/quest/m1/smoke-cdn.md) - jsDelivr failures retain their response evidence and any first-party cause is fixed +- [Moxygen minimal interop](/quest/m1/smoke-moxygen.md) - announce-subscribe passes and the smoke lane stops hiding its failure +- [Public relay diagnosis](/quest/m1/smoke-relays.md) - optional failed cells get attributed causes and focused first-party follow-ups - [FETCH max-delay](/quest/m1/fetch-max-delay.md) - historical readers obey publisher max-age and an optional tighter reader budget, including while holding a group - [Draft-20 FETCH edge-case backport](/quest/m1/fetch-edge-cases.md) - backport the final-object and response-group fixes to a later 0.17 patch after main lands - [Subscribe-close backport](/quest/m1/subscribe-close-backport.md) - the same fix and the `race` loser fix on `release`, so closing a subscription during setup leaves no unhandled rejection in a later 0.17 patch diff --git a/quest/m1/smoke-cdn.md b/quest/m1/smoke-cdn.md new file mode 100644 index 00000000000..9608de6937c --- /dev/null +++ b/quest/m1/smoke-cdn.md @@ -0,0 +1,30 @@ +# [S] Diagnose jsDelivr failures in published browser smoke + +## Goal + +Smoke's jsDelivr lane explains a failed module load with enough evidence to +distinguish CDN delivery from a package or media regression, and any +reproducible first-party defect is fixed at its source. + +## Plan + +In the [2026-10-15 Smoke run](https://github.com/moq-dev/smoke/actions/runs/38739639896), +apt and Docker each fail five jsDelivr subscriber cells. Early navigations +time out; later browser logs report a missing CORS header on +`https://cdn.jsdelivr.net/npm/@moq/watch/element/+esm`. The same CDN works +for later cells and the cargo job. A subsequent request returned HTTP 200 +with `Access-Control-Allow-Origin: *`. + +The failed responses' status and body were not retained, so a transient CDN +failure is a hypothesis, not a demonstrated root cause. Work belongs in +moq-dev/smoke, whose client installs and browser navigation own the evidence. +Capture the failing request/response and page error context in CI artifacts, +then reproduce before changing package loading or publication. + +Preserve the real CDN lane, latest-package policy, and red media cells. +Do not add exchange retries, longer timeouts, or a local bundle fallback. +Wire any diagnostic regression into smoke's CI. No product documentation +change is needed for test diagnostics alone. + +The maintainer requested fixes or quests for the investigated failures on +2026-10-15; the exact CDN cause remains open. diff --git a/quest/m1/smoke-moxygen.md b/quest/m1/smoke-moxygen.md new file mode 100644 index 00000000000..8715c1bfa47 --- /dev/null +++ b/quest/m1/smoke-moxygen.md @@ -0,0 +1,34 @@ +# [S] Moxygen announce-subscribe works through moq-relay + +## Goal + +moq-dev/smoke's minimal Moxygen interop client passes `announce-subscribe` +through moq-relay on each transport and draft the lane claims to cover, +and that failure no longer hides behind `continue-on-error`. + +## Plan + +The [2026-10-15 Moxygen job](https://github.com/moq-dev/smoke/actions/runs/38739639896/job/116437673088) +reports success while its script fails. Both WebTransport and raw QUIC +negotiate draft-16, then TAP case 4 (`announce-subscribe`) fails with +`Subscribe failed: Session closed`. The other five cases pass. The workflow +explicitly marks the step `continue-on-error` for this known mismatch. + +Reproduce the minimal lane and trace the failed request before choosing a +protocol or routing change. Fix a first-party defect in moq-dev/moq with a +regression at its source, then verify smoke's Git-head lane. An upstream +client defect needs a reduced reproducer and a clearly attributed result; +posting outside moq-dev and kixelated requires maintainer approval. + +Remove the exception once the full claimed lane passes. Do not accept a +session close as successful media exchange or hide the failing case. Any +wire change keeps published drafts compatible and updates Rust, JS, and +the matching draft together. + +This minimal six-case lane is independent of the larger moq-test +passthrough conformance work. The maintainer requested fixes or quests for +the investigated failures on 2026-10-15. + +## Related + +- [moq-transport passthrough](/quest/m1/ietf-extension/README.md) - broader object forwarding and moq-test conformance diff --git a/quest/m1/smoke-relays.md b/quest/m1/smoke-relays.md new file mode 100644 index 00000000000..7b1a00388b0 --- /dev/null +++ b/quest/m1/smoke-relays.md @@ -0,0 +1,38 @@ +# [M] Attribute public relay interop failures + +## Goal + +The failed optional cells in moq-dev/smoke's public relay matrix have +reproducible, attributed causes. First-party interoperability bugs have +focused fixes or their own quests; unavailable endpoints and unsupported +peer behavior remain explicit results rather than unexplained timeouts. + +## Plan + +All eight required `cdn.moq.dev` cells pass in the +[2026-10-15 relay job](https://github.com/moq-dev/smoke/actions/runs/38739639896/job/116437673069). +Optional failures affect imquic, Cloudflare draft-14 and draft-16, +moqtail draft-22 and draft-18, moqx, Moxygen, quiche-moq, and stitcher-moq. +These results do not make the workflow fail, but a green required-relay gate +does not prove those peers interoperable. + +Use the per-cell logs and published report to distinguish connection or +endpoint availability from protocol, catalog, and media failures. Reproduce +against a local peer when possible; a public endpoint's state alone cannot +identify whose implementation is wrong. Preserve the publisher/subscriber +and transport distinctions: some peers fail only browser publishing or +particular subscribers. + +Keep required versus optional policy unchanged. Do not remove endpoints, +skip failing supported versions, add exchange retries, or widen timeouts to +make the table green. The result of this diagnosis may be several +independently landable fixes or quests, rather than one cross-peer patch. +No external posts are authorized outside moq-dev and kixelated. + +The maintainer requested fixes or quests for the investigated failures on +2026-10-15. The minimal Moxygen client failure has its own owner. + +## Related + +- [Moxygen minimal interop](/quest/m1/smoke-moxygen.md) - fixes the local announce-subscribe failure +- [Draft-22 release line](/quest/m0/release-22/README.md) - prior imquic release compatibility work diff --git a/quest/m2/release/README.md b/quest/m2/release/README.md index dd313a48be3..64a57aa3685 100644 --- a/quest/m2/release/README.md +++ b/quest/m2/release/README.md @@ -27,6 +27,7 @@ production stability proven merely because upstream artifacts published. ## Required - [Cut and publish](/quest/m2/release/cut.md) - independently executable after m1; release-triggered publication +- [Published catalog readers](/quest/m2/release/catalog-readers.md) - released Go and JS clients accept the current Rust publisher's live catalog in smoke; an earlier release-line patch may satisfy it - [Published assets](/quest/m2/release/assets-release.md) - npm carries hostable worklets - [C++ publication](/quest/m2/release/cpp-release.md) - archives and matching OBS plugin publish and install - [Generated C publication](/quest/m2/release/c-publish.md) - released archives run the C samples and interop client diff --git a/quest/m2/release/catalog-readers.md b/quest/m2/release/catalog-readers.md new file mode 100644 index 00000000000..b3fbbbac05f --- /dev/null +++ b/quest/m2/release/catalog-readers.md @@ -0,0 +1,36 @@ +# [S] Published catalog readers accept current live media + +## Goal + +The latest published Go and JavaScript clients read live media from the +current Rust publisher in moq-dev/smoke's Nix channel. Incompatible optional +archive metadata does not make an otherwise playable catalog unreadable. + +## Plan + +The [2026-10-15 Smoke run](https://github.com/moq-dev/smoke/actions/runs/38739639896) +fails only the Nix Rust publisher against Go and all five JS readers: +`archive.track` is missing because current catalogs use `archive.timelines`. +The released Rust, Python, Kotlin, C, and GStreamer readers pass. + +Parser tolerance landed on main in #5485 and on the Rust release line in +#5520. Released `@moq/hang` 0.5.2 and the Go module installed in that run +still require the old archive shape. Verify which published artifacts carry +the corrected parser and advance their publication through the normal +release process. This quest does not authorize a breaking release cut or +version bumps outside that process. + +Complete against packages installed from their registries in smoke, keeping +every MoQ package at latest. Do not pin an older publisher, skip these cells, +or suppress catalog errors. Direct archive validation and invalid media +remain strict. Remove the `catalog-archive` compatibility exception only +after measuring that its released JS reader accepts current catalogs. + +The maintainer requested fixes or quests for the investigated failures on +2026-10-15. Publication is tracked separately from the completed parser fix, +in the existing release-execution act rather than as a prerequisite of m1. + +## Related + +- [Release execution](/quest/m2/release/README.md) - owns publication and installed-artifact verification +- [Release-line patch](/quest/m0/release-22/README.md) - the current patch publication owner From 87e5d6f1160f2d3a759dd22c032f1f07c9a09583 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 15 Oct 2026 16:02:33 -0700 Subject: [PATCH 2/2] quest: note the 0.17 patch publishes @moq/hang (#5590) Co-Authored-By: Claude Opus 5.5 --- quest/m2/release/catalog-readers.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/quest/m2/release/catalog-readers.md b/quest/m2/release/catalog-readers.md index b3fbbbac05f..6ccc97009dd 100644 --- a/quest/m2/release/catalog-readers.md +++ b/quest/m2/release/catalog-readers.md @@ -15,10 +15,11 @@ The released Rust, Python, Kotlin, C, and GStreamer readers pass. Parser tolerance landed on main in #5485 and on the Rust release line in #5520. Released `@moq/hang` 0.5.2 and the Go module installed in that run -still require the old archive shape. Verify which published artifacts carry -the corrected parser and advance their publication through the normal -release process. This quest does not authorize a breaking release cut or -version bumps outside that process. +still require the old archive shape. The next 0.17 patch publishes +`@moq/hang` with that parser (decided in #5590, owned by the release-line +patch). Verify which published artifacts carry the corrected parser and +advance any others through the normal release process. This quest does not +authorize a breaking release cut or version bumps outside that process. Complete against packages installed from their registries in smoke, keeping every MoQ package at latest. Do not pin an older publisher, skip these cells,