Skip to content

quest: link the two outside conditions main rejects #4666

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.

Sign up for GitHub

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
kixelated merged 1 commit into from
Oct 1, 2026
+18 −2
Merged

quest: link the two outside conditions main rejects #4666

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions quest/m1/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,7 @@ QUIC studies there on that rule.
- [IETF drain before close](/quest/m1/ietf-drain-before-close.md) - moq-transport sessions deliver finished tracks before a graceful close, as moq-lite does
- [Close waits for the tail](/quest/m1/close-tail.md) - on lite-07, `close()` returns `Ok` only after each subscriber FINs its Subscribe Stream, having read the track to its end
- [moq play drain tail](/quest/m1/play-drain-tail.md) - retired renditions and finite tracks play their last 10 ms of audio
- [A moq-relay release refuses --cluster-mesh](/quest/m1/relay-mesh-refusal-release.md) - the release that lets the cluster flag shims go
- [web-transport-moq 1.3.3 ships noq#24](/quest/m1/web-transport-moq-release.md) - the release that carries the close-capsule fix
- [WebTransport close upstream](/quest/m1/wt-close-upstream.md) - web-transport-moq delivers the close capsule itself, and moq-tokio's `CLOSE_LINGER` is deleted
- [Browser close code](/quest/m1/browser-close-code.md) - a playwright case proves the page reads a relay's close code and reason, on every web-transport backend
Expand Down
2 changes: 1 addition & 1 deletion quest/m1/admission-bench.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,4 +20,4 @@ wakes.

## Required

- The wildcard line (moq-dev/moq#4403) lands on main, where the walk lives
- [Wildcard](/quest/m0/wildcard/README.md) - the line the admission walk lives on
2 changes: 1 addition & 1 deletion quest/m1/cluster-shims.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,4 +18,4 @@ Public API: removes two hidden `cluster::Config` fields. Wire: none.

## Required

- A moq-relay release carrying the `--cluster-mesh` refusal from #4601
- [A moq-relay release refuses --cluster-mesh](/quest/m1/relay-mesh-refusal-release.md) - the release that carries the last refusal
15 changes: 15 additions & 0 deletions quest/m1/relay-mesh-refusal-release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# [XS] A moq-relay release refuses --cluster-mesh

## Goal

A `moq-relay` release on crates.io carries
[#4601](https://github.com/moq-dev/moq/pull/4601), which refuses
`--cluster-mesh` at startup with a pointer to its replacement.

This quest tracks a condition outside the repository. When it holds, delete
this quest and every `Required` entry that links it.

## Plan

As of 2026-10-01 the newest release is moq-relay 0.15.8 (2026-09-28), cut
before #4601 merged.
Loading