From 1daa9563739b4eeb1e46d05bc5f6004970f06949 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 20 Oct 2026 18:25:02 -0700 Subject: [PATCH 1/5] quest: plan the release shutdown backport Co-Authored-By: Claude Opus 5.5 --- quest/m0/README.md | 1 + quest/m0/ffi-shutdown-backport.md | 38 +++++++++++++++++++++++++++++++ 2 files changed, 39 insertions(+) create mode 100644 quest/m0/ffi-shutdown-backport.md diff --git a/quest/m0/README.md b/quest/m0/README.md index bed1c473d7e..e66a59120db 100644 --- a/quest/m0/README.md +++ b/quest/m0/README.md @@ -85,6 +85,7 @@ Each lands its fixes in its own PR and plans only what needs a decision. - [CI cost and latency](/quest/m0/ci/README.md) - cloud CI runs only in the merge queue as one `just ci` pass, expensive checks run nightly and gate `release`, caches move to R2, and runners are chosen last - [Release builds link](/quest/m0/release-link.md) - the Linux zigbuild release binaries and moq-gst packages link again after the 2026-10-11 nixpkgs bump, so the next release cut can publish - [Namespace advert errors](/quest/m0/namespace-advert-error.md) - one PUBLISH_NAMESPACE stream failing withdraws only that namespace instead of closing the Rust session +- [Release shutdown backport](/quest/m0/ffi-shutdown-backport.md) - `release` publishes a non-breaking moq-ffi with an async `drain()` and qmux sessions on the QUIC stream limit - [Broadcast epochs](/quest/m0/broadcast-epoch/README.md) - every first-party publisher that can restart mints a fresh route epoch, the newest wins a path, and only routes with the same epoch resume a subscription - [Benchmark regression table](/quest/m0/bench-site.md) - the nightly benchmark page is one light table where red and green flag regressions and improvements beyond each series' noise - [Performance audit](/quest/m0/audit-perf.md) - benchmarks that regressed since the last run are explained, fixed, or planned, and unbenched hot paths get coverage diff --git a/quest/m0/ffi-shutdown-backport.md b/quest/m0/ffi-shutdown-backport.md new file mode 100644 index 00000000000..0bc5da66835 --- /dev/null +++ b/quest/m0/ffi-shutdown-backport.md @@ -0,0 +1,38 @@ +# [S] Backport draining shutdown and the qmux stream limit to release + +## Goal + +The `release` line publishes a non-breaking moq-ffi 0.4.x (wheel, Swift, and +Kotlin) and moq-tokio whose sessions can drain before closing and whose qmux +sessions accept the QUIC stream limit: + +- An async `MoqSession.drain()` delivers finished tracks within one second + and returns any delivery error, as `main`'s async `shutdown()` does + (7bbac3272, with 03fb0d1c1, f9de31167, and #5558's explicit Lite 07 test). + The sync `shutdown()` stays `cancel(0)`. +- qmux sessions get the QUIC stream limit (#5609) instead of the 100-stream + default. + +Check: release-plz publishes the release commits, and PyPI's newest moq-ffi +contains both. + +## Plan + +Decided 2026-10-20 (maintainer): additive `drain()` on `release` rather than +backporting async `shutdown()` as-is. Why: making `shutdown()` async breaks +the 0.4.x Python, Swift, and Kotlin bindings. `main` keeps async `shutdown()` +and gains no `drain()`; callers move to it at the next breaking cut. + +Follow the backport workflow. #5609 cherry-picks as is. The drain backport +adapts 7bbac3272's session close to the `release` line's moq-net and keeps +its tests, renamed to `drain()`. Run the Python, Swift, and Kotlin binding +tests. The qmux credit fix is out of scope: it arrives with +[qmux on the QUIC stream state machine](/quest/m1/quic-qmux.md). + +Public API: additive (`MoqSession.drain()` and its binding wrappers). Wire: +none. + +## Related + +- [Release builds link](/quest/m0/release-link.md) - the release binaries + must link for the cut that publishes this From 4e8c845ffe830b7a63b78a39caad1effb1e83d7c Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 20 Oct 2026 18:41:23 -0700 Subject: [PATCH 2/5] quest: cover every FFI binding and publication in the shutdown backport Co-Authored-By: Claude Opus 5.5 --- quest/m0/ffi-shutdown-backport.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/quest/m0/ffi-shutdown-backport.md b/quest/m0/ffi-shutdown-backport.md index 0bc5da66835..581d9ec8076 100644 --- a/quest/m0/ffi-shutdown-backport.md +++ b/quest/m0/ffi-shutdown-backport.md @@ -13,8 +13,9 @@ sessions accept the QUIC stream limit: - qmux sessions get the QUIC stream limit (#5609) instead of the 100-stream default. -Check: release-plz publishes the release commits, and PyPI's newest moq-ffi -contains both. +Check: release-plz publishes the release commits, and the newest moq-ffi on +PyPI, the Swift package, and Maven Central contains both. Swift and Kotlin +publish from their own tag workflows, so check each. ## Plan @@ -25,8 +26,10 @@ and gains no `drain()`; callers move to it at the next breaking cut. Follow the backport workflow. #5609 cherry-picks as is. The drain backport adapts 7bbac3272's session close to the `release` line's moq-net and keeps -its tests, renamed to `drain()`. Run the Python, Swift, and Kotlin binding -tests. The qmux credit fix is out of scope: it arrives with +its tests, renamed to `drain()`. Follow the Cross-Package Sync row for +`rs/moq-ffi`: every binding and its docs gain `drain()`, or the PR says why +one has none. Run each binding's tests and `just test interop --all`. The +qmux credit fix is out of scope: it arrives with [qmux on the QUIC stream state machine](/quest/m1/quic-qmux.md). Public API: additive (`MoqSession.drain()` and its binding wrappers). Wire: From 2005051c62ce29236e015325d3bcfb040ed82fb7 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 20 Oct 2026 18:48:00 -0700 Subject: [PATCH 3/5] quest: gate the stream-limit backport on qmux 0.5.3 Co-Authored-By: Claude Opus 5.5 --- quest/m0/README.md | 1 + quest/m0/ffi-shutdown-backport.md | 12 +++++++++++- quest/m0/qmux-0.5.3.md | 17 +++++++++++++++++ quest/m1/quic-qmux.md | 4 +++- 4 files changed, 32 insertions(+), 2 deletions(-) create mode 100644 quest/m0/qmux-0.5.3.md diff --git a/quest/m0/README.md b/quest/m0/README.md index a6c3c16c683..c53d6e0edaf 100644 --- a/quest/m0/README.md +++ b/quest/m0/README.md @@ -85,6 +85,7 @@ Each lands its fixes in its own PR and plans only what needs a decision. - [CI cost and latency](/quest/m0/ci/README.md) - cloud CI runs only in the merge queue as one `just ci` pass, expensive checks run nightly and gate `release`, caches move to R2, and runners are chosen last - [Release builds link](/quest/m0/release-link.md) - the Linux zigbuild release binaries and moq-gst packages link again after the 2026-10-11 nixpkgs bump, so the next release cut can publish - [Namespace advert errors](/quest/m0/namespace-advert-error.md) - one PUBLISH_NAMESPACE stream failing withdraws only that namespace instead of closing the Rust session +- [qmux 0.5.3](/quest/m0/qmux-0.5.3.md) - crates.io publishes qmux 0.5.3 with the builder session config the release backport of #5609 needs - [Release shutdown backport](/quest/m0/ffi-shutdown-backport.md) - `release` publishes a non-breaking moq-ffi with an async `drain()` and qmux sessions on the QUIC stream limit - [Broadcast epochs](/quest/m0/broadcast-epoch/README.md) - every first-party publisher that can restart mints a fresh route epoch, the newest wins a path, and only routes with the same epoch resume a subscription - [Performance audit](/quest/m0/audit-perf.md) - benchmarks that regressed since the last run are explained, fixed, or planned, and unbenched hot paths get coverage diff --git a/quest/m0/ffi-shutdown-backport.md b/quest/m0/ffi-shutdown-backport.md index 581d9ec8076..d4e2fef782c 100644 --- a/quest/m0/ffi-shutdown-backport.md +++ b/quest/m0/ffi-shutdown-backport.md @@ -24,7 +24,13 @@ backporting async `shutdown()` as-is. Why: making `shutdown()` async breaks the 0.4.x Python, Swift, and Kotlin bindings. `main` keeps async `shutdown()` and gains no `drain()`; callers move to it at the next breaking cut. -Follow the backport workflow. #5609 cherry-picks as is. The drain backport +Decided 2026-10-20 (maintainer): keep #5609 in the backport, on a qmux +0.5.3 published from web-transport's `qmux-v0.5.x`. Why: `release` locks +qmux 0.5.2, which lacks the builder session config #5609 uses, and +moq-dev/web-transport#427 already carries that config for 0.5. + +Follow the backport workflow. #5609 moves `release` to qmux 0.5.3 and takes +its builder session config instead of 0.6.3's. The drain backport adapts 7bbac3272's session close to the `release` line's moq-net and keeps its tests, renamed to `drain()`. Follow the Cross-Package Sync row for `rs/moq-ffi`: every binding and its docs gain `drain()`, or the PR says why @@ -35,6 +41,10 @@ qmux credit fix is out of scope: it arrives with Public API: additive (`MoqSession.drain()` and its binding wrappers). Wire: none. +## Required + +- [qmux 0.5.3](/quest/m0/qmux-0.5.3.md) - crates.io publishes qmux 0.5.3 with the builder session config #5609 needs + ## Related - [Release builds link](/quest/m0/release-link.md) - the release binaries diff --git a/quest/m0/qmux-0.5.3.md b/quest/m0/qmux-0.5.3.md new file mode 100644 index 00000000000..d579224bcd6 --- /dev/null +++ b/quest/m0/qmux-0.5.3.md @@ -0,0 +1,17 @@ +# [XS] Publish qmux 0.5.3 + +## Goal + +crates.io carries qmux 0.5.3 with moq-dev/web-transport#427, the builder +session config the `release` line needs to port #5609. A maintainer +publishes it; delete this quest once it is on crates.io. + +Check: `cargo info qmux@0.5.3` resolves, and the `qmux-v0.5.3` tag on +moq-dev/web-transport contains #427's merge. + +## Plan + +Waiting on a maintainer. #427 merged on web-transport's `qmux-v0.5.x`, which +has no release-plz, so the publish is manual: one commit bumps qmux to 0.5.3 +with a CHANGELOG entry, then `cargo publish -p qmux` and push the +`qmux-v0.5.3` tag. diff --git a/quest/m1/quic-qmux.md b/quest/m1/quic-qmux.md index a8a9616c837..2fd5486eff9 100644 --- a/quest/m1/quic-qmux.md +++ b/quest/m1/quic-qmux.md @@ -89,7 +89,9 @@ the fork plan the same day kept it there. Decided 2026-10-20 (maintainer): moved to m1. moq stops depending on the web-transport repo, so the qmux credit and close fixes ship here instead of as upstream releases and pin bumps; the bug stays on main until this lands. -The release line keeps its current qmux and gets no backport. +The release line gets no backport of the credit and close fixes; the +stream-limit port in the [release shutdown backport](/quest/m0/ffi-shutdown-backport.md) +is the exception. ## Required From 7bdc885eddf2a7f6b71e9c3c094ad02732e4a6c1 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 20 Oct 2026 19:27:49 -0700 Subject: [PATCH 4/5] quest: qualify the drain guarantee and publish the wrappers Co-Authored-By: Claude Opus 5.5 --- quest/m0/ffi-shutdown-backport.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/quest/m0/ffi-shutdown-backport.md b/quest/m0/ffi-shutdown-backport.md index d4e2fef782c..00acadeeceb 100644 --- a/quest/m0/ffi-shutdown-backport.md +++ b/quest/m0/ffi-shutdown-backport.md @@ -6,16 +6,20 @@ The `release` line publishes a non-breaking moq-ffi 0.4.x (wheel, Swift, and Kotlin) and moq-tokio whose sessions can drain before closing and whose qmux sessions accept the QUIC stream limit: -- An async `MoqSession.drain()` delivers finished tracks within one second +- An async `MoqSession.drain()` drains finished tracks within one second and returns any delivery error, as `main`'s async `shutdown()` does (7bbac3272, with 03fb0d1c1, f9de31167, and #5558's explicit Lite 07 test). - The sync `shutdown()` stays `cancel(0)`. + Explicit `moq-lite-07-wip` waits for the peer to receive the tail; older + Lite versions, including the default lite-06, and IETF wait only for + transport ACKs. The sync `shutdown()` stays `cancel(0)`. - qmux sessions get the QUIC stream limit (#5609) instead of the 100-stream default. Check: release-plz publishes the release commits, and the newest moq-ffi on PyPI, the Swift package, and Maven Central contains both. Swift and Kotlin -publish from their own tag workflows, so check each. +publish from their own tag workflows, so check each. The newest hand-written +wrappers (`moq-rs`, the Swift and Kotlin libraries, and the other wrappers +that gain `drain()`) expose it too. ## Plan @@ -34,7 +38,9 @@ its builder session config instead of 0.6.3's. The drain backport adapts 7bbac3272's session close to the `release` line's moq-net and keeps its tests, renamed to `drain()`. Follow the Cross-Package Sync row for `rs/moq-ffi`: every binding and its docs gain `drain()`, or the PR says why -one has none. Run each binding's tests and `just test interop --all`. The +one has none. Wrapper workflows skip versions already published, so bump +each changed wrapper's human-owned version (CONTRIBUTING's Versions). Run +each binding's tests and `just test interop --all`. The qmux credit fix is out of scope: it arrives with [qmux on the QUIC stream state machine](/quest/m1/quic-qmux.md). From 0128af2258ddcba92ab1a472e11fb313a92c6157 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 20 Oct 2026 19:34:37 -0700 Subject: [PATCH 5/5] quest: leave the Go wrapper version to CI Co-Authored-By: Claude Opus 5.5 --- quest/m0/ffi-shutdown-backport.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/quest/m0/ffi-shutdown-backport.md b/quest/m0/ffi-shutdown-backport.md index 00acadeeceb..aa36cac9e7b 100644 --- a/quest/m0/ffi-shutdown-backport.md +++ b/quest/m0/ffi-shutdown-backport.md @@ -39,8 +39,9 @@ adapts 7bbac3272's session close to the `release` line's moq-net and keeps its tests, renamed to `drain()`. Follow the Cross-Package Sync row for `rs/moq-ffi`: every binding and its docs gain `drain()`, or the PR says why one has none. Wrapper workflows skip versions already published, so bump -each changed wrapper's human-owned version (CONTRIBUTING's Versions). Run -each binding's tests and `just test interop --all`. The +each changed wrapper's human-owned version (CONTRIBUTING's Versions). Leave +`go/wrapper/VERSION` alone: CI derives Go's patch, and `drain()` is +additive. Run each binding's tests and `just test interop --all`. The qmux credit fix is out of scope: it arrives with [qmux on the QUIC stream state machine](/quest/m1/quic-qmux.md).