Repository navigation
quest: first pass of the pre-cut feature review, and its follow-ups #8764
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
603edc4
chore(quest): claim quest/m3/release/feature-review.md
kixelated d8efdef
quest: first pass of the pre-cut feature review, and its follow-ups
kixelated 8491aad
quest: transient pull cycles account for #8734's re-pinned ring fixture
kixelated c21dea7
quest: record the maintainer's picks on the feature review's follow-ups
kixelated 9935cc9
Merge remote-tracking branch 'origin/main' into quest/m3/release/feat…
kixelated 8d1bbc9
quest: drop links to quests main finished, and mark route-trace-valid…
kixelated File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,24 @@ | ||
| # [S] Nightly's benchmark jobs finish within their hour | ||
|
|
||
| ## Goal | ||
|
|
||
| Nightly's "Rust bench targets" and "JS benchmarks" jobs finish inside their | ||
| timeout and publish their series again, and the Nightly triage counts a | ||
| cancelled job as a failure, so a job that times out every night is owned. | ||
|
|
||
| ## Plan | ||
|
|
||
| Found 2026-11-14 by the [feature review](/quest/m3/release/feature-review.md). | ||
| "Rust bench targets" was cancelled 10 of the 14 nights before 2026-11-14 | ||
| (every night since 11-09), and "JS benchmarks" 11 of 14 (every night since | ||
| 11-04); in run 43601796176 the Rust job was still compiling the paired base | ||
| in `/tmp/moq-bench-base.*` when `timeout-minutes: 60` | ||
| (`.github/workflows/nightly.yml`) cancelled it. A cancelled job is not a | ||
| failed one, so the failure-based triage never named either; about 2 | ||
| job-hours a night produce nothing. Find why the paired base builds cold | ||
| though the previous Nightly built that same commit | ||
| ([moq-dev/moq#8763](https://github.com/moq-dev/moq/pull/8763) notes cache | ||
| units that were "not looked up"), fix that at the cause, and only then split | ||
| or trim the jobs if they still overrun. Never raise the timeout to fit. | ||
|
|
||
| Public API: none. Wire: none. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| # [S] A peer's listing churn yields to the host's tasks, unquarantined | ||
|
|
||
| ## Goal | ||
|
|
||
| `js/net`'s "a flood of a peer's listing churn yields to the host's tasks" | ||
| (`js/net/src/lite/tracks.test.ts`) runs again and passes under a loaded | ||
| `just check`, fixed at its cause on a mocked clock or an awaited event, never | ||
| with a looser budget. | ||
|
|
||
| ## Plan | ||
|
|
||
| Found 2026-11-14 by the [feature review](/quest/m3/release/feature-review.md)'s | ||
| first pass: [moq-dev/moq#8355](https://github.com/moq-dev/moq/pull/8355) | ||
| skipped it after it timed out at 5 s in 2 of 30 full `js/net` runs under 48 | ||
| CPU burners, while that PR fixed a different test, so no quest owned the | ||
| quarantine. Reproduce under the same load first, then decide whether the | ||
| budget loop or the test's wait is at fault, following this epic's rules. | ||
|
|
||
| Public API: none. Wire: none. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| # [S] moq-mux's container consumer tests run on the simulated clock | ||
|
|
||
| ## Goal | ||
|
|
||
| The tests in `rs/moq-mux/src/container/consumer.rs` that depend on time run | ||
| under `#[kio::test]`'s simulated clock instead of `#[tokio::test]` on the real | ||
| one, and `gap_in_group_sequence_recovery` stops flaking in the merge queue. | ||
|
|
||
| ## Plan | ||
|
|
||
| Found 2026-11-14 by the [feature review](/quest/m3/release/feature-review.md): | ||
| queue run 43557751216 failed `gap_in_group_sequence_recovery` ("Expected >= 4 | ||
| frames, got 2", 0.386 s) on a quest-only PR the day after this epic's three | ||
| loaded runs passed. It is a plain `#[tokio::test]` with a 100 ms max delay, | ||
| like most of the file's 115 tests, about 40 of which set a millisecond | ||
| `with_max`. `KIO_DENY_HOST_TIMERS` catches timers fired on the host clock, not | ||
| reads of it, which is the gap REVIEW.md's Tests section names. Convert the | ||
| time-dependent tests, as `rs/AGENTS.md` asks; tests with no timing stay as | ||
| they are. | ||
|
|
||
| Public API: none. Wire: none. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,34 @@ | ||
| # [XS] Binding playout-delay tests stop racing the native wall clock | ||
|
|
||
| ## Goal | ||
|
|
||
| The Go, Swift, Kotlin, and Dart "audio consumer reports its playout delay" | ||
| tests no longer hang when the host stalls between the writes and the first | ||
| read, matching the Python and Rust fixes | ||
| ([moq-dev/moq#8050](https://github.com/moq-dev/moq/pull/8050), | ||
| [moq-dev/moq#8566](https://github.com/moq-dev/moq/pull/8566)). | ||
|
|
||
| ## Plan | ||
|
|
||
| Found 2026-11-14 by the [feature review](/quest/m3/release/feature-review.md). | ||
| A fixed consumer with `max` zero skips a group by the native wall clock, so a | ||
| read that starts more than the 80 ms warmup after group 1 arrives waits out its | ||
| timeout (#8566 reproduced it with a 200 ms stall). Still latent in | ||
| `go/wrapper/moq_test.go` (`Delay{Min: 80ms}`, zero Max), Swift's | ||
| `SmokeTests.swift` (`max: 0`), and Dart's `moq_test.dart` (`max` defaults to | ||
| zero); Kotlin's | ||
| [moq-dev/moq#8475](https://github.com/moq-dev/moq/pull/8475) kept `max = 0` | ||
| and added a writer that loops until a read lands, which is a retry around the | ||
| cause. Pass `max: None` (or the language's unset value) to both consumers, and | ||
| delete Kotlin's writer loop. | ||
|
|
||
| As a rule for new tests, assert native timing and decoding once, | ||
| in moq-ffi's Rust tests, and limit wrapper tests to the code each wrapper | ||
| owns (record mapping, cancellation, async adapters, lifetimes). Six copies of | ||
| this test took three separate fixes over a week, and three copies were still | ||
| unfixed. | ||
|
|
||
| Decided 2026-11-14 (maintainer, pick on [moq-dev/moq#8764](https://github.com/moq-dev/moq/pull/8764)): ✅ (a) fix all four copies, and from now on native timing and decoding are asserted once, in moq-ffi's Rust tests, while wrapper tests cover only the code each wrapper owns; this quest writes that rule into `rs/moq-ffi/AGENTS.md` (rejected: (b) delete the four copies now). | ||
|
|
||
| Public API: none. Wire: none. | ||
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| # [S] Relay bitrate cap tests run on the QUIC simulator | ||
|
|
||
| ## Goal | ||
|
|
||
| The tokio half of `rs/moq-relay/tests/integration/bitrate_caps.rs` runs on | ||
| `quic::driver::sim` and asserts the capped transfer's time within a window in | ||
| simulated time, so a regression that throttles far below the cap fails, and | ||
| the tests stop waiting on the real clock. | ||
|
|
||
| ## Plan | ||
|
|
||
| Found 2026-11-14 by the [feature review](/quest/m3/release/feature-review.md). | ||
| The tests assert only `elapsed >= 700ms` and poll every 10 ms on real time, | ||
| because [moq-dev/moq#7535](https://github.com/moq-dev/moq/pull/7535) chose | ||
| real sockets while no QUIC simulator existed; one landed in | ||
| [moq-dev/moq#8709](https://github.com/moq-dev/moq/pull/8709) | ||
| (`rs/moq-relay/tests/integration/quic_sim.rs`). The io_uring half stays on | ||
| real sockets. | ||
|
|
||
| Public API: none. Wire: none. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,29 @@ | ||
| # [M] A fetch survives the track ending on a relay chain | ||
|
|
||
| ## Goal | ||
|
|
||
| On a relay chain, a fetch already in flight when the publisher ends the track | ||
| still delivers the rest of its group, and a fetch asked of a copy that has | ||
| completed goes on the wire instead of waiting out the subscriber's budget. | ||
| Both `residual_*` tests in `rs/moq-net/tests/integration/failover_chain.rs` | ||
| flip to assert delivery, and `EndedRelay.cfg`'s open finding is gone. | ||
|
|
||
| ## Plan | ||
|
|
||
| Found 2026-11-14 by the [feature review](/quest/m3/release/feature-review.md): | ||
| the tests pin two bugs `verify/failover/FailoverChain.tla` rules out, and no | ||
| quest or PR owns them. | ||
|
|
||
| - `residual_ending_the_track_fails_a_fetch_in_flight` (`NoSkipWhileHeld`): | ||
| E's fetch of group 0 is in flight through B when the track ends; B's copy, | ||
| asked from group 1, completes, which cancels B's fetch from P, so E's read | ||
| fails though P still writes the rest. | ||
| - `residual_a_fetch_from_a_completed_copy_never_leaves_the_relay` | ||
| (`Settles`): reading group 0 on after E's track ended asks B's completed | ||
| copy, and that fetch never goes on the wire, a hang bounded only by the | ||
| subscriber's budget. | ||
|
|
||
| Replay `EndedRelay.cfg` on the real stack, fix at the cause, and run | ||
| `/verify-failover` and `/verify-resume` on the head. | ||
|
|
||
| Public API: none. Wire: none. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,38 @@ | ||
| # [S] A first session refused at SETUP fails fast | ||
|
|
||
| ## Goal | ||
|
|
||
| A client whose first session is refused right after ALPN (a rejected token on | ||
| moq-lite 03 or later, which has no server SETUP to wait for) reports the | ||
| refusal and stops, as a first dial that reaches no relay does, instead of | ||
| redialing forever. Rust and JS behave the same, and the docs promise only | ||
| what the code does. | ||
|
|
||
| ## Plan | ||
|
|
||
| Found 2026-11-14 by the [feature review](/quest/m3/release/feature-review.md). | ||
| `Reconnect` (`rs/moq-net/src/reconnect.rs`) sets `established` as soon as the | ||
| transport connects, and `walk_failed` fails fast only while `!established`, | ||
| though its comment says that catches "a refused credential". A relay's | ||
| `MalformedAuthToken` close then reaches `closed()`, which backs off and redials | ||
| forever under `Backoff::timeout: None`. | ||
| [moq-dev/moq#8694](https://github.com/moq-dev/moq/pull/8694) hit exactly this | ||
| (one refusal a second in the relay log) and changed the interop test rather | ||
| than the client. `doc/bin/gstreamer.md` ("only reports `failed` on an answer | ||
| redialing can't change, such as a rejected token") and the comments in | ||
| `rs/moq-gst/src/sink/session.rs` are false since | ||
| [moq-dev/moq#8618](https://github.com/moq-dev/moq/pull/8618). | ||
|
|
||
| Mark a session established only once it clears | ||
| `Backoff::healthy`, which `Retry::settle` already computes, so no error kind | ||
| is read; mirror it in `js/net`'s `#establishedHref`; update `Handover.tla` | ||
| through `/verify-reconnect`; fix the gst docs and comments and | ||
| `.claude/skills/verify-reconnect/SKILL.md`'s stale refusal exception. | ||
| #8618 settled that a refusal of a session that was live retries; this changes | ||
| only a first session that never became healthy. | ||
|
|
||
| Decided 2026-11-14 (maintainer, pick on [moq-dev/moq#8764](https://github.com/moq-dev/moq/pull/8764)): ✅ (a) a session is established only once it clears `Backoff::healthy` (rejected: (b) keep retrying and correct only the docs). | ||
|
|
||
| Public API: none. Wire: none. Behavior: a client whose first session is | ||
| refused before it is healthy ends with that error. | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,16 @@ | ||
| # [XS] A flight asks upstream with its riders' priority | ||
|
|
||
| ## Goal | ||
|
|
||
| A flight's upstream fill (`track::board` in `rs/moq-net/src/model/track.rs`) | ||
| asks with the priority and delay of the reader that boarded it, as every other | ||
| fill does, so a late joiner's replay is not ranked below all live traffic on a | ||
| congested upstream link. | ||
|
|
||
| ## Plan | ||
|
|
||
| Found 2026-11-14 by the [feature review](/quest/m3/release/feature-review.md): | ||
| `board` hardcodes `fill::Asking { priority: 0, max_delay: None }`. Pass the | ||
| rider's `Preferences` in, and add a test that the fill carries them. | ||
|
|
||
| Public API: none. Wire: none. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| # [XS] The merge gate runs repository tooling tests only when tooling changes | ||
|
|
||
| ## Goal | ||
|
|
||
| A diff that touches no repository tooling stops paying for the `gh` module's | ||
| tests in the merge queue, while Nightly's full `gate` job still runs them | ||
| every night. | ||
|
|
||
| ## Plan | ||
|
|
||
| Found 2026-11-14 by the [feature review](/quest/m3/release/feature-review.md). | ||
| `sh/dispatch.sh` registers `module gh ''`, an empty pattern that matches every | ||
| diff, in `lane=bun` after the JS checks. In queue run 43634181288 (a | ||
| `flake.lock` bump) that lane was the whole 497 s run, with `test gh` at 224 s; | ||
| in 43622947541 the bun lane (409 s, `test gh` 220 s) outlasted the Rust lane. | ||
| Its wall time is about twice its CPU time, and it failed none of 34 queue | ||
| failures sampled from 11-12 to 11-14. Three files take 65 s of its 115 s | ||
| locally (`dispatch-query.test.py`, `nightly.test.py`, `rs/select.test.py`). | ||
|
|
||
| Give `module gh` a path pattern covering what its tests | ||
| read (`sh/`, `bench/`, `.github/`, justfiles, `test/smoke/`, the Go publish | ||
| scripts) and keep the actionlint and zizmor lints on workflow changes; run | ||
| the three slow files in parallel if the lane still leads. | ||
|
|
||
| Decided 2026-11-14 (maintainer, pick on [moq-dev/moq#8764](https://github.com/moq-dev/moq/pull/8764)): ✅ (a) scope the module to tooling paths, with Nightly's `gate` as the backstop (rejected: (b) keep it on every diff and only parallelize). | ||
|
|
||
| Public API: none. Wire: none. | ||
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| # [XS] JavaScript ignores FILL_TIMEOUT as Rust does | ||
|
|
||
| ## Goal | ||
|
|
||
| A JS publisher accepts any FILL_TIMEOUT a moq-transport subscriber sends, up to | ||
| the varint maximum, and ignores it as the Rust publisher does, instead of | ||
| refusing the subscription with `malformed(FILL_PARAMETERS)`. | ||
|
|
||
| ## Plan | ||
|
|
||
| Found 2026-11-14 by the [feature review](/quest/m3/release/feature-review.md): | ||
| `js/net/src/ietf/filter.ts` and `parameters.ts` decode it with `toNumber`, | ||
| which throws above 2^53, while Rust skips it and keeps only whether it was | ||
| present (`rs/moq-net/src/ietf/fetch.rs`). Nothing in JS reads `fillTimeout` | ||
| since [moq-dev/moq#8445](https://github.com/moq-dev/moq/pull/8445) removed | ||
| JS FETCH serving, so keep presence only, delete the numeric field and its | ||
| encode path, and flip `js/net/src/integers.test.ts`'s refusal. Also fix | ||
| `fetch.rs`'s comment saying the request "is refused", which contradicts | ||
| `doc/concept/standard.md` ("accept and ignore"). | ||
|
|
||
| Public API: none. Wire: none (the JS side stops refusing a valid value). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| # [S] The JavaScript byte pool carries only what a JS caller can reach | ||
|
|
||
| ## Goal | ||
|
|
||
| `js/net`'s per-broadcast byte pool keeps idle expiry, drop-run expiry, and the | ||
| per-group frame tail cap, and carries byte eviction only if a JS consumer sets | ||
| a capacity. Code that no production path reaches leaves the bundle. | ||
|
|
||
| ## Plan | ||
|
|
||
| Found 2026-11-14 by the [feature review](/quest/m3/release/feature-review.md). | ||
| The pool's capacity defaults to infinity (`js/net/src/cache.ts`), every pool | ||
| is built without one (`broadcast.ts`, `track.ts`), and `resize` has no | ||
| non-test caller, so `Pool.accrue` always returns `undefined` and `#payDebt`, | ||
| reader debt, group `#shed`, and the debt calls in `track.ts` run only in | ||
| tests. [moq-dev/moq#8177](https://github.com/moq-dev/moq/pull/8177) said so | ||
| ("byte eviction runs only for a pool given one. Today only tests do that"), | ||
| yet [moq-dev/moq#8294](https://github.com/moq-dev/moq/pull/8294), | ||
| [moq-dev/moq#8440](https://github.com/moq-dev/moq/pull/8440), and | ||
| [moq-dev/moq#8673](https://github.com/moq-dev/moq/pull/8673) kept building | ||
| on it. Rust differs: the relay sets a capacity. Expiry alone already bounds | ||
| the drop set (#8294). | ||
|
|
||
| This revisits the pool quest's decision to port it "with no new setting" | ||
| (deleted by #8177), with the evidence that two weeks on nothing reaches the | ||
| path. | ||
|
|
||
| Delete byte debt, shed, reader debt, and run billing from JS, | ||
| keeping the expiries; restore them from git with a consumer. | ||
|
|
||
| Decided 2026-11-14 (maintainer, pick on [moq-dev/moq#8764](https://github.com/moq-dev/moq/pull/8764)): ✅ (a) delete the unreachable eviction (rejected: (b) expose `capacity`; (c) keep it for parity). | ||
|
|
||
| Public API: none. Wire: none. |
File renamed without changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| # [S] A socket endpoint's every ending runs its cleanup | ||
|
|
||
| ## Goal | ||
|
|
||
| `moq_net::socket::Endpoint` models its lifecycle as one state whose ended | ||
| variant carries its error, and every ending, including the route broadcast | ||
| closing, goes through `close()`, so track streams already handed out end with | ||
| it as they do in JS. `is_endpoint` reaches moq-ffi, every binding, and the | ||
| socket guide. | ||
|
|
||
| ## Plan | ||
|
|
||
| Found 2026-11-14 by the [feature review](/quest/m3/release/feature-review.md). | ||
| In `rs/moq-net/src/model/socket.rs`, `Handler::None` means both "not made | ||
| yet" and "ended", with `end: Option<Error>` stored beside it, and `poll_end` | ||
| returns `Closed` when a route broadcast closes without recording it or running | ||
| `close()`: when the origin shuts down, streams already handed out stay open | ||
| until the application drops the `Endpoint`. Shape it as REVIEW.md's State | ||
| section asks (`Open { .. } | Closed(Error)`). | ||
| [moq-dev/moq#8468](https://github.com/moq-dev/moq/pull/8468)'s | ||
| `socket::is_endpoint` exists only in Rust and JS. | ||
|
|
||
| Public API: moq-ffi and every binding gain `is_endpoint`. Wire: none. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Route an unhealthy close of a not-yet-established session through the fail-fast path.
The plan changes
establishedso that it means "clearedhealthy". That flag gates onlywalk_failed. A session that closes before it becomes healthy reachesclosed(), which does not readestablishedand callsback_offatrs/moq-net/src/reconnect.rs:1092. That call schedules a redial, so the refusal does not end with its error.Update the plan so that
closed()also ends the policy withdone(Err(err))when no session has been established and the closing session was not healthy. Keep the predecessor handling atclosed()ahead of this check. TheMigratingpath still applies to a draining predecessor, so this change must not discard it.