From d46dfa82b22d51468e2961f38f98e9f23ec6e0af Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sun, 15 Nov 2026 02:19:11 -0800 Subject: [PATCH 1/3] chore(quest): claim quest/m0/release-qmux-credit.md Quest-Claim: a63b5bfe530b84fd From 4f964ff635c63c117f192cdda36a23b521a945d8 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Sun, 15 Nov 2026 03:33:05 -0800 Subject: [PATCH 2/3] quest: the qmux credit backport is open, wait on its merge and cut Co-Authored-By: Claude Sonnet 5.5 --- quest/m0/release-qmux-credit.md | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/quest/m0/release-qmux-credit.md b/quest/m0/release-qmux-credit.md index 1b40b991053..b3a8c191570 100644 --- a/quest/m0/release-qmux-credit.md +++ b/quest/m0/release-qmux-credit.md @@ -32,6 +32,13 @@ published API. `main` needs no change. `Cargo.toml` and `Cargo.lock`. `bun.lock` moves `@moq/qmux` to 0.3.5, and `@moq/net` requires `^0.3.5`, so a fresh install of the next `@moq/net` can't resolve a leaky version. +- ✅ Done in [moq-dev/moq#8808](https://github.com/moq-dev/moq/pull/8808) on + `release`: the pins, the `@moq/net` 0.4.8 bump (it also ships the two + unpublished `@moq/net` backports merged since 0.4.7, #8035 and #8346), the + audit, and the relay validation (the publisher direction fails on 0.5.3 after + 7 to 9 cancels and passes 120 on 0.5.4; the viewer direction is shown by + `@moq/qmux`'s own credit tests, failing on 0.3.3 and passing on 0.3.5, since + loopback never leaves data in flight after a cancel). - ✅ Audit before cutting (maintainer, 2026-11-14). The PR audits everything the next release ships since each package's last published version, not only this bump: anything else merged to `release` since moq-relay 0.17.16 and the JS @@ -54,10 +61,13 @@ published API. `main` needs no change. ## Waiting -- moq-dev/web-transport: `qmux` 0.5.4 on crates.io and `@moq/qmux` 0.3.5 on - npm. Check `cargo info qmux@0.5.4` (run outside a workspace) and - `npm view @moq/qmux@0.3.5 version`. Their quests are web-transport's - `quest/a0/qmux-05-recv-credit.md` and `quest/a0/qmux-js-release.md`. +- Maintainer: merge [moq-dev/moq#8808](https://github.com/moq-dev/moq/pull/8808) + into `release` (its merge publishes `@moq/net` 0.4.8, which requires + `@moq/qmux` `^0.3.5`), then merge the release-plz PR it triggers for `qmux` + 0.5.4's dependents (`moq-tokio`, `moq-relay`, and theirs). Check + `npm view @moq/net@0.4.8 version` and that `cargo info moq-relay` names a + version newer than 0.17.16. Finish this quest then by deleting it with + `quest rm`. Not an agent step: a merge to `release` publishes. ## Related From e500d0eca2312226b7a6642c3995d6762f4a2241 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Mon, 16 Nov 2026 02:48:51 -0800 Subject: [PATCH 3/3] quest: finish the qmux credit quest, #8808 carries the record Co-Authored-By: Claude Sonnet 5.5 --- quest/m0/release-qmux-credit.md | 77 --------------------------------- quest/m3/release/cut.md | 4 +- quest/m3/send-credit-stalls.md | 2 +- 3 files changed, 3 insertions(+), 80 deletions(-) delete mode 100644 quest/m0/release-qmux-credit.md diff --git a/quest/m0/release-qmux-credit.md b/quest/m0/release-qmux-credit.md deleted file mode 100644 index b3a8c191570..00000000000 --- a/quest/m0/release-qmux-credit.md +++ /dev/null @@ -1,77 +0,0 @@ -# [S] The release line returns QMux receive credit - -## Goal - -The next `release` patch ships `qmux` 0.5.4 and `@moq/qmux` 0.3.5. Both fix -moq-dev/web-transport's receive-credit leak -([moq-dev/web-transport#507](https://github.com/moq-dev/web-transport/issues/507)). -In the leaky versions, a stream dropped or cancelled with unread data never -returns that data's connection credit (`MAX_DATA`). Once about one connection -window (1 MiB) of it has piled up, the sender cannot write on any stream of -that connection, but the session stays up and logs nothing. - -On the release line that hits every QMux session in both directions: - -- **Publisher to relay.** The relay cancels its upstream subscription when the - last downstream subscriber leaves, often in the middle of a group. Each group - stream it drops leaks its unread bytes. Eventually the publisher can send - nothing, while the relay's requests still reach it. -- **Relay to browser.** A viewer on the WebSocket fallback cancels group streams - it skips, so the browser's window shrinks the same way. - -`main` is unaffected: its in-tree `rs/qmux` (on `moq-quic`) and `js/qmux` already -credit stopped streams, late data, and the reset gap. - -## Plan - -Planned 2026-11-14 (maintainer, /quest-plan in moq-dev/web-transport). Per -[RELEASE.md](/RELEASE.md), this is a backport PR onto `release` that keeps the -published API. `main` needs no change. - -- On `release`, the workspace pin moves from `qmux` 0.5.3 to 0.5.4 in - `Cargo.toml` and `Cargo.lock`. `bun.lock` moves `@moq/qmux` to 0.3.5, and - `@moq/net` requires `^0.3.5`, so a fresh install of the next `@moq/net` can't - resolve a leaky version. -- ✅ Done in [moq-dev/moq#8808](https://github.com/moq-dev/moq/pull/8808) on - `release`: the pins, the `@moq/net` 0.4.8 bump (it also ships the two - unpublished `@moq/net` backports merged since 0.4.7, #8035 and #8346), the - audit, and the relay validation (the publisher direction fails on 0.5.3 after - 7 to 9 cancels and passes 120 on 0.5.4; the viewer direction is shown by - `@moq/qmux`'s own credit tests, failing on 0.3.3 and passing on 0.3.5, since - loopback never leaves data in flight after a cancel). -- ✅ Audit before cutting (maintainer, 2026-11-14). The PR audits everything the - next release ships since each package's last published version, not only this - bump: anything else merged to `release` since moq-relay 0.17.16 and the JS - packages' last releases, plus the two dependency diffs. The web-transport - release PRs audit those, so link their audits. Record the audit in the PR - body. A finding that should hold the release goes to the maintainer before the - release-plz PR merges. -- Validate on the built release-line relay over WebSocket, in both directions, - against the old and new pins: - - A publisher session gets well over 1 MiB of mid-group cancels from - subscribers that join and leave. A later subscriber still receives groups, - which fails on 0.5.3. - - A JS viewer cancels groups past one window. It keeps receiving, which fails - on 0.3.3. - - Run the viewer past 100 cancelled streams. `@moq/qmux` 0.3.5 holds a - cancelled stream's slot until the peer sends FIN or RESET_STREAM, and qmux - 0.5.x resets only when its app polls the stream. Group streams do that. - Confirm the relay's other streams to the browser (announce, subscribe) don't - sit idle holding slots. - -## Waiting - -- Maintainer: merge [moq-dev/moq#8808](https://github.com/moq-dev/moq/pull/8808) - into `release` (its merge publishes `@moq/net` 0.4.8, which requires - `@moq/qmux` `^0.3.5`), then merge the release-plz PR it triggers for `qmux` - 0.5.4's dependents (`moq-tokio`, `moq-relay`, and theirs). Check - `npm view @moq/net@0.4.8 version` and that `cargo info moq-relay` names a - version newer than 0.17.16. Finish this quest then by deleting it with - `quest rm`. Not an agent step: a merge to `release` publishes. - -## Related - -- [Send-credit stalls](/quest/m3/send-credit-stalls.md) - names this kind of - stall in session stats on `main` -- [Walk-away cancels](/quest/m3/walkaway-cancel.md) - the publisher logged the - unanswerable requests as "internal error" diff --git a/quest/m3/release/cut.md b/quest/m3/release/cut.md index 097f453f8dd..2964a2b4f2f 100644 --- a/quest/m3/release/cut.md +++ b/quest/m3/release/cut.md @@ -15,8 +15,8 @@ minor up per later API or wire cut, following [Versions](/RELEASE.md#versions), including packages that did not change. `@moq/qmux` and the Rust `qmux` crate are exempt from that version (`version.json`), so check each against its registry by hand: npm already has `@moq/qmux` 0.3.3 and 0.3.4, published -from moq-dev/web-transport, and 0.3.5 follows for -[the release line's credit fix](/quest/m0/release-qmux-credit.md), while `js/qmux` is at 0.3.3. Publishing 0.3.3 +from moq-dev/web-transport, and 0.3.5 for +[the release line's credit fix](https://github.com/moq-dev/moq/pull/8808), while `js/qmux` is at 0.3.3. Publishing 0.3.3 fails, and `workspace:^` would resolve `@moq/net`'s dependency to web-transport's latest 0.3.x, a different API. `js/qmux` must publish above that; the maintainer picks the version (found 2026-11-07 by the API shape audit). diff --git a/quest/m3/send-credit-stalls.md b/quest/m3/send-credit-stalls.md index 2eaff65dec4..95ad5012cd9 100644 --- a/quest/m3/send-credit-stalls.md +++ b/quest/m3/send-credit-stalls.md @@ -19,7 +19,7 @@ Decided 2026-11-14 (maintainer, /quest-plan): - ✅ A counter in session stats (rejected: a warning log after N seconds, which needs a constant; both together). - ✅ `main` only (rejected: backport to `release`). It adds API, and on the - release line [the receive-credit fix](/quest/m0/release-qmux-credit.md) + release line [the receive-credit fix](https://github.com/moq-dev/moq/pull/8808) removes the cause. Today, a received DATA_BLOCKED is only logged at trace