Skip to content

chore(quest): retire merged binding linger work #6229

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 5 commits into from
Oct 22, 2026
Merged

chore(quest): retire merged binding linger work #6229

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
604a3c0
chore(quest): claim linger-ffi retirement
kixelated Oct 22, 2026
54fcb06
chore(quest): retire merged binding linger work
kixelated Oct 22, 2026
6d6974f
Merge origin/main into quest/m1/linger-ffi
kixelated Oct 22, 2026
d184885
Merge origin/main into quest/m1/linger-ffi
kixelated Oct 22, 2026
ffe83fb
Merge origin/main into quest/m1/linger-ffi
kixelated Oct 22, 2026
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: 0 additions & 1 deletion quest/m1/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,6 @@ lite-07 stream type here.
- [Recovery verdicts](/quest/m1/recovery-verdicts.md) - group recovery refetches only on errors a new copy can fix, so a repeating error ends the group instead of looping
- [Rust resume holds a declared end](/quest/m1/resume-rust-end.md) - a resumed Rust track keeps a declared end across copies, dedupes flapping copies, and judges retention inside the reader's window
- [WebGPU on Safari](/quest/m1/webgpu-safari.md) - the WebGPU renderer is verified on Safari 26 for macOS and iOS
- [Binding linger](/quest/m1/linger-ffi.md) - `moq-ffi` and every binding finish a broadcast cleanly, so subscribers drain it until its media is stale
- [Interop finish](/quest/m1/interop-finish.md) - the interop matrix proves a clean broadcast finish across implementations
- [Exporters follow a rendition to a new track](/quest/m1/export-rendition-rebind.md) - the fMP4, TS, MKV and FLV exporters rebuild a rendition whose resolved `track` or `broadcast` changes under the same ID
- [fMP4 import unwraps to Legacy](/quest/m1/fmp4-import-unwrap.md) - fMP4 and HLS imports publish per-sample `Legacy` frames unless `--passthrough` asks for CMAF, and no first-party producer defaults to CMAF
Expand Down
1 change: 0 additions & 1 deletion quest/m1/c/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,6 @@ That change owns its C tests and `MIGRATE.md` entries; other API reshaping stays
Decided 2026-10-20 (maintainer): m1 quests that change the C API
([exact binding timestamps](/quest/m1/binding-timestamps.md),
[scope track priority](/quest/m1/track-priority-scope.md),
[binding linger](/quest/m1/linger-ffi.md),
[Rust identity enforcement](/quest/m1/catalog-identity-rs.md), and
[dynamic subscribe ranges](/quest/m1/subscribe-ranges/dynamic.md)) Require this
line and land their C half on the generated package, so C users break once.
Expand Down
10 changes: 3 additions & 7 deletions quest/m1/interop-finish.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,15 +9,11 @@ in any implementation's linger shows up as a red cell.

## Plan

From [moq-dev/moq#6151](https://github.com/moq-dev/moq/pull/6151), which
gave js/net `Broadcast.Producer.finish()`. Rust, JS, and the bindings each
have a finish once their linger quests land. Drive it from the existing
Rust, JS ([moq-dev/moq#6151](https://github.com/moq-dev/moq/pull/6151)),
and the bindings ([moq-dev/moq#6157](https://github.com/moq-dev/moq/pull/6157))
each have a finish. Drive it from the existing
interop clients rather than adding a new harness, and assert both halves:
the late tail arrives and the end is clean. The new case's cells show up
in the nightly report at <https://git.moq.dev/interop/>.

Public API: none. Wire: none.

## Required

- [Binding linger](/quest/m1/linger-ffi.md) - bindings finish a broadcast, so the binding interop clients can
45 changes: 0 additions & 45 deletions quest/m1/linger-ffi.md
View file
Open in desktop

This file was deleted.

4 changes: 0 additions & 4 deletions quest/m2/go-first-dial-failure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,3 @@ while their examples only use `Moq.connect`, which never hands back a
binding PRs that also touch those pages have landed.

@chatgpt-codex-connector chatgpt-codex-connector Bot Oct 22, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep auth as a prerequisite for the Go quest

Removing the final ## Required section makes this quest ready immediately, even though its plan still says these documentation edits must wait for both the linger and auth binding PRs. quest/m1/auth/bindings-polish.md only lists this quest as Related, so it creates no dependency, and that m1 auth work remains open; a quest runner can now start this work concurrently and conflict on the same Kotlin and Dart pages. Replace the retired linger edge with an explicit dependency on Binding auth polish.

Useful? React with 👍 / 👎.


Public API: Go additive. Wire: none.

## Required

- [Binding linger](/quest/m1/linger-ffi.md) - touches the same binding docs
Loading