From cf3a3f261729b916b55517b09124f8c0c2c579ee Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 22 Oct 2026 22:08:25 -0700 Subject: [PATCH 1/3] chore(quest): claim quest/m1/interop-coverage/js-namespace-done.md Quest-Claim: c8e12e0678ffadff From d1f8388ab96f1cced6dc8a06b05b54924ec91551 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 22 Oct 2026 23:59:50 -0700 Subject: [PATCH 2/3] quest: the JS namespace lifecycle cell waits on an @moq/net patch The cause is @moq/net 0.4.4 withdrawing PUBLISH_NAMESPACE with a FIN on drafts 17+, fixed on main by #5483 and backported to release by #6518. What remains is bumping the runner's JS client once that patch publishes. Co-Authored-By: Claude Opus 5.5 --- quest/m1/interop-coverage/README.md | 2 +- .../m1/interop-coverage/js-namespace-done.md | 32 ++++++++++++------- quest/m1/interop-coverage/runner-cases.md | 9 +++--- 3 files changed, 26 insertions(+), 17 deletions(-) diff --git a/quest/m1/interop-coverage/README.md b/quest/m1/interop-coverage/README.md index a5fb1cfc35c..9dd1a835745 100644 --- a/quest/m1/interop-coverage/README.md +++ b/quest/m1/interop-coverage/README.md @@ -41,7 +41,7 @@ coverage on `main` at `3ab6cbf81d`. ## Required - [Runner cases](/quest/m1/interop-coverage/runner-cases.md) - our runner clients' data-subgroup-basic and subscribe-namespace-lifecycle land upstream and go green on the report -- [JS namespace lifecycle](/quest/m1/interop-coverage/js-namespace-done.md) - moq-dev-js subscribe-namespace-lifecycle sees NAMESPACE_DONE with publisher and subscriber in one process +- [JS namespace lifecycle](/quest/m1/interop-coverage/js-namespace-done.md) - the runner's moq-dev-js client moves to an `@moq/net` that withdraws namespaces by reset, so subscribe-namespace-lifecycle passes on Cloudflare draft-18 and aiomoqt - [JS subgroup data through imquic](/quest/m1/interop-coverage/js-imquic-objects.md) - moq-dev-js data-subgroup-basic receives objects from imquic over WebTransport - [Late join and FETCH](/quest/m1/interop-coverage/late-join.md) - a late subscriber gets the current group from object 0, and a standalone FETCH returns a past group exactly - [Control cases](/quest/m1/interop-coverage/control.md) - GOAWAY redirect, TRACK_STATUS, datagrams, and request-ID limits pass across implementations diff --git a/quest/m1/interop-coverage/js-namespace-done.md b/quest/m1/interop-coverage/js-namespace-done.md index 7d45234b377..8b7c197e96d 100644 --- a/quest/m1/interop-coverage/js-namespace-done.md +++ b/quest/m1/interop-coverage/js-namespace-done.md @@ -1,22 +1,30 @@ -# [S] JS namespace lifecycle passes with both halves in one process +# [XS] The runner's JS client withdraws namespaces by reset ## Goal -The runner's moq-dev-js `subscribe-namespace-lifecycle` case passes against -Cloudflare draft-18 and aiomoqt, where today the subscriber never sees -NAMESPACE_DONE. If the cause is in the relay under test, it is reported -upstream and the cell is classified instead. +Condition: an `@moq/net` release carries +[moq-dev/moq#6518](https://github.com/moq-dev/moq/pull/6518), the `release` +backport of [moq-dev/moq#5483](https://github.com/moq-dev/moq/pull/5483). +Check with `npm view @moq/net version` and that release's changelog; the +pending patch is [moq-dev/moq#6501](https://github.com/moq-dev/moq/pull/6501). + +Then bump `@moq/net` in the moq-dev-js client of +[englishm/moq-interop-runner](https://github.com/englishm/moq-interop-runner) +to it, so `subscribe-namespace-lifecycle` passes against Cloudflare +draft-18 and aiomoqt, and delete this quest once that PR merges. ## Plan -Found in the runs for -[englishm/moq-interop-runner#173](https://github.com/englishm/moq-interop-runner/pull/173) -on 2026-10-22. It fails only when the JS publisher and subscriber share one -process. Each half passes with a Rust counterpart, and two separate Bun -processes pass, so suspect state the two `js/net` sessions share in one -process before suspecting the relays. A fix in `js/net` gets a test there. +`@moq/net` 0.4.4 withdraws a PUBLISH_NAMESPACE on drafts 17+ with FIN plus +STOP_SENDING, which draft-18 §3.3.2 does not allow. Both relays end the +namespace only on RESET_STREAM, so the subscriber never sees NAMESPACE_DONE +until the publisher's session closes. The case passed from two processes +only because the exiting publisher closed its session. `main` has sent the +reset since #5483, and the runner's client passes against both relays when +built on `main` or on #6518. The Rust client already passes. -Public API: unknown until the cause is found. Wire: none expected. +The interop audit's standing approval covers PRs touching the `moq-dev-*` +builds. ## Related diff --git a/quest/m1/interop-coverage/runner-cases.md b/quest/m1/interop-coverage/runner-cases.md index 886c15fbbdd..28131207fc7 100644 --- a/quest/m1/interop-coverage/runner-cases.md +++ b/quest/m1/interop-coverage/runner-cases.md @@ -51,9 +51,10 @@ from the stale client image. Rebuilt from the runner's current source, it passes against moxygen and Cloudflare draft-18. Cloudflare draft-14 has no SUBSCRIBE_NAMESPACE, so that cell is unsupported. -Two moq-dev-js cells from the runs for #173 still fail, with causes not -yet found: -[JS namespace lifecycle in one process](/quest/m1/interop-coverage/js-namespace-done.md) -and [JS subgroup data through imquic](/quest/m1/interop-coverage/js-imquic-objects.md). +Two moq-dev-js cells from the runs for #173 still fail: +[JS namespace lifecycle](/quest/m1/interop-coverage/js-namespace-done.md), +which waits on an `@moq/net` patch, and +[JS subgroup data through imquic](/quest/m1/interop-coverage/js-imquic-objects.md), +with its cause not yet found. Public API: none. Wire: none. From ef826815e9474b9d32e93b01797fba572f6c7f1d Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Fri, 23 Oct 2026 09:52:40 -0700 Subject: [PATCH 3/3] quest: wait on the next @moq/net patch carrying #6518 Co-Authored-By: Claude Opus 5.5 --- .../m1/interop-coverage/js-namespace-done.md | 29 +++++++++++-------- 1 file changed, 17 insertions(+), 12 deletions(-) diff --git a/quest/m1/interop-coverage/js-namespace-done.md b/quest/m1/interop-coverage/js-namespace-done.md index c96f23083a7..391ca655f77 100644 --- a/quest/m1/interop-coverage/js-namespace-done.md +++ b/quest/m1/interop-coverage/js-namespace-done.md @@ -2,11 +2,15 @@ ## Goal -Condition: an `@moq/net` release carries -[moq-dev/moq#6518](https://github.com/moq-dev/moq/pull/6518), the `release` -backport of [moq-dev/moq#5483](https://github.com/moq-dev/moq/pull/5483). -Check with `npm view @moq/net version` and that release's changelog; the -pending patch is [moq-dev/moq#6501](https://github.com/moq-dev/moq/pull/6501). +Condition: the next `@moq/net` patch release, 0.4.6 or later, ships from +`release` carrying [moq-dev/moq#6518](https://github.com/moq-dev/moq/pull/6518), +the JS-only `release` backport of +[moq-dev/moq#5483](https://github.com/moq-dev/moq/pull/5483). It merged as +`350dee5520` after the 0.4.5 bump +([moq-dev/moq#6501](https://github.com/moq-dev/moq/pull/6501)) had shipped +without it. Check that `npm view @moq/net version` is above 0.4.5 and that +`git log origin/release -- js/net/package.json` shows the bump to it after +`350dee5520`. Releases are cut separately; this quest bumps nothing. Then bump `@moq/net` in the moq-dev-js client of [englishm/moq-interop-runner](https://github.com/englishm/moq-interop-runner) @@ -15,13 +19,14 @@ draft-18 and aiomoqt, and delete this quest once that PR merges. ## Plan -`@moq/net` 0.4.4 withdraws a PUBLISH_NAMESPACE on drafts 17+ with FIN plus -STOP_SENDING, which draft-18 §3.3.2 does not allow. Both relays end the -namespace only on RESET_STREAM, so the subscriber never sees NAMESPACE_DONE -until the publisher's session closes. The case passed from two processes -only because the exiting publisher closed its session. `main` has sent the -reset since #5483, and the runner's client passes against both relays when -built on `main` or on #6518. The Rust client already passes. +`@moq/net` 0.4.5 and earlier withdraw a PUBLISH_NAMESPACE on drafts 17+ +with FIN plus STOP_SENDING, which draft-18 §3.3.2 does not allow. Both +relays end the namespace only on RESET_STREAM, so the subscriber never sees +NAMESPACE_DONE until the publisher's session closes. The case passed from +two processes only because the exiting publisher closed its session. `main` +has sent the reset since #5483, and the runner's client passes against both +relays when built on `main` or on #6518. The Rust client already passes, so +the maintainer kept the backport JS-only. The interop audit's standing approval covers PRs touching the `moq-dev-*` builds.