Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
5 changes: 0 additions & 5 deletions quest/m0/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,6 @@ publisher that can restart mints a fresh epoch, so #4741 stalls nobody.
The release API gates (#3829..#3878) and the release that followed them are
done. moq.pro pins this repository's `release` line, so the release gate below
also keeps #4741 from reaching it early.
The Pronto GPU integration lives in moq.pro.

Relay hardening left in m0 is idle fronts: per-session request caps landed
in #4820, and the rest of the 2026-09-29 DoS review moved to m1 with
Expand Down Expand Up @@ -63,7 +62,3 @@ remain and no release waits on them.
- [web-transport releases the qmux fixes](/quest/m0/qmux-credit-upstream.md) - waiting on moq-dev/web-transport#412 and #413 to merge and ship, which qmux credit bumps to
- [qmux credit](/quest/m0/qmux-credit.md) - qmux returns connection credit for dropped and stopped streams and delivers its close frame, on both lines
- [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

## Related

- [Pronto GPU integration](https://github.com/moq-dev/moq.pro/tree/main/quest/m0/pronto/gpu) - CARLA bridge, release adoption and desktop installation
12 changes: 7 additions & 5 deletions quest/m0/broadcast-epoch/stats-split.md
Original file line number Diff line number Diff line change
Expand Up @@ -113,16 +113,18 @@ Decided 2026-10-05 (planned from moq-dev/moq.pro#2202):
same format it reads.

Decided 2026-10-08: if prefix tracks and self counters hold up the rest,
split them into a follow-up quest and land totals, sessions, and the map
retirement first.
split them into a follow-up quest and land totals and sessions first. The
per-path map retirement moves with prefix tracks and self counters into that
follow-up: the maps are the only per-path source until prefix tracks exist,
and moq.pro's Broadcasts page reads prefix tracks the moment the maps retire,
so a release that retires them first is one moq.pro cannot pin.

Public API: `moq-stats` producer and consumer types. Wire: stats track names
and payloads.

MoQ Pro adopts it when it pins the release: billing reads totals, its
Broadcasts page reads one prefix per visible row and group header, its `announced` probe
reads totals only, and its customer stats feed serves this format summed
across nodes.
Broadcasts page reads one prefix per visible row and group header, and its
customer stats feed serves this format summed across nodes.

## Related

Expand Down
6 changes: 4 additions & 2 deletions quest/m0/qmux-credit.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,8 +48,9 @@ Remaining here, once both ship: bump `main` to that 0.6.x and backport
breaking change. Sized XS (2026-10-08), since the fixes live upstream and only
the pin bumps remain here.

Why m0: the WebSocket fallback and the edge-to-core `tls://` links (#4816)
both run on qmux, and MoQ drops streams constantly.
Why m0: the WebSocket fallback, moq.pro's Voice, and the edge-to-core
`tls://` links (#4816) that moq.pro's cluster sessions move to all run on
qmux, and MoQ drops streams constantly.

Public API: none. Wire: none.

Expand All @@ -60,3 +61,4 @@ Public API: none. Wire: none.
## Related

- [qmux on the QUIC stream state machine](/quest/m2/quic-qmux.md) - replaces these stream maps later
- [moq.pro: edge-to-core qmux](https://github.com/moq-dev/moq.pro/blob/main/quest/m1/edge-core/qmux-credit.md) - the long-lived cluster links that need this
2 changes: 2 additions & 0 deletions quest/m1/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,8 @@ were done or not worth their cost.
- [Audio group duration](/quest/m1/audio-group-duration.md) - audio groups span at least 20 ms by default, so small frames don't mint a group each
- [Browser interop cells](/quest/m1/interop-browser-timeouts.md) - `go -> js` and `python -> js` pass, fixed at the cause rather than by a longer timeout
- [Wire compatibility](/quest/m1/wire-compat.md) - a nightly run tests this checkout against the last published release for tokens, session wire, and catalog/container
- [Kotlin wrapper POMs](/quest/m1/kt-ffi-pom.md) - Maven builds of `dev.moq:moq` resolve a published moq-ffi instead of the missing `0.0.0-dev`
- [Homebrew moq-gst](/quest/m1/gst-brew-path.md) - `brew install moq-gst` installs the plugin from the tarball's `lib/gstreamer-1.0/`
- [Same-epoch importers](/quest/m1/hop-aligned-import.md) - importers sharing one `--epoch` and fed one stream publish identical groups and timestamps, so failover between a redundant pair survives
- [moq.sh deploys from CI](/quest/m1/moq-sh-deploy.md) - the first `release` run of the moq.sh workflow deploys with the Workers Editor token
- [Plan: untimed verbatim PES](/quest/m1/plan-ts-pes-untimed.md) - decide how a verbatim TS track carries a PES that has no PTS, then write the implementation quest
Expand Down
5 changes: 3 additions & 2 deletions quest/m1/dogfood-assets.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,9 @@ CSP is out of scope: neither site adds a policy.

Decided in planning: the maintainer wants hosted mode dogfooded, not just the
pin bump. No CSP on either site. The moq.dev change is a direct PR, since that
repo has no quest tree. pronto/web is skipped: it renders video only and never
loads a worklet.
repo has no quest tree. The moq.pro side is part of its
[package adoption](https://github.com/moq-dev/moq.pro/blob/main/quest/m1/ship-dev.md).
pronto/web is skipped: it renders video only and never loads a worklet.

Guidance:

Expand Down
27 changes: 27 additions & 0 deletions quest/m1/gst-brew-path.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# [S] Homebrew installs the moq-gst plugin

## Goal

`brew install moq-gst` installs the plugin and `gst-inspect-1.0 moq` finds
it. Today the formula installs `lib/libgstmoq.*`, but the release tarball
keeps the plugin under `lib/gstreamer-1.0/`, so the glob matches nothing and
the formula installs nothing without an error. The published tap formula
(0.4.12) matches the template.

## Plan

- `.github/homebrew/Formula/moq-gst.rb.tmpl` installs from
`lib/gstreamer-1.0/`, the layout `rs/moq-gst/build.sh` packages and
`.github/workflows/moq-gst.yml` smoke-tests. Its caveats and `test do`
block move to the same path.
- Check on macOS whether Homebrew's `gstreamer` already scans
`$(brew --prefix)/lib/gstreamer-1.0`. If it does, install there and drop the
`GST_PLUGIN_PATH` caveat.
- [moq#4555](https://github.com/moq-dev/moq/pull/4555) carried this fix with a
Nix wrapper change and closed unmerged on 2026-09-29. Nothing has owned it
since.
- Regression check: the moq-gst workflow's macOS job installs the rendered
formula against the tarball it just built and runs `brew test moq-gst`, so a
formula and tarball that disagree fail before release.

Public API: none. Wire: none.
42 changes: 42 additions & 0 deletions quest/m1/kt-ffi-pom.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
# [S] Kotlin wrapper POMs name a published moq-ffi

## Goal

The `dev.moq:moq-jvm` and `dev.moq:moq-android` POMs on Maven Central depend
on a published `moq-ffi` variant, so a Maven build resolves the wrapper.
Today 0.5.0 and 0.5.1 depend on `moq-ffi-jvm` and `moq-ffi-android` version
`0.0.0-dev`, which was never published, so every Maven consumer fails to
resolve. A PR check refuses a generated POM naming that version.

## Plan

Checked against Maven Central on 2026-10-08:

- `moq-jvm` 0.5.0 and 0.5.1 depend on `moq-ffi-jvm:0.0.0-dev`, and
`moq-android` 0.5.1 on `moq-ffi-android:0.0.0-dev`. `moq-jvm` 0.4.5 depended
on `moq-ffi` `[0.3,0.4)`.
- Gradle consumers resolve: the `.module` metadata and the root `moq` POM
keep `MOQ_FFI_RANGE` (`[0.4.3,0.5)`).

Cause: `kt/moq/build.gradle.kts` substitutes `dev.moq:moq-ffi` with the
sibling `:moq-ffi` project in every configuration, and the target POMs take
that project's coordinates and version, `moqffi.version=0.0.0-dev` in
`kt/gradle.properties`. Its comment that the published POM keeps the range
holds only for the root POM. The 0.4 line had the same substitution, so a
Kotlin or Gradle upgrade since changed the POM rewrite.

Options:

- Keep the substitution out of the publication's configurations, so target
POMs carry `MOQ_FFI_RANGE` on the target artifacts (recommended: Maven
consumers float to new bindings patches as Gradle consumers do).
- Publish with `moqffi.version` set to the current FFI release, which pins
Maven consumers to one bindings patch.

Test: the `release-kt-lib.yml` PR dry-run inspects the POMs that
`publishToMavenLocal` writes and fails when a `dev.moq` dependency names
`0.0.0-dev`. Ship it as a wrapper patch: that workflow publishes only when
`moq.version` changes. Maven Central is immutable, so 0.5.0 and 0.5.1 stay
broken.

Public API: none. Wire: none.
2 changes: 1 addition & 1 deletion quest/m1/lite07-finalize.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,4 +85,4 @@ is published; older versions are unchanged.

- [The moq.pro mesh runs lite-07](/quest/m3/lite07-mesh.md) - the deployment condition that follows this
- [Wire compatibility](/quest/m1/wire-compat.md) - the nightly covers lite-07 once a release carries it
- [moq.pro: lite-07 on cluster dials](https://github.com/moq-dev/moq.pro/blob/main/quest/m1/lite07.md) - the mesh rollout that adopts the finalized version, and the customer rollout after it
- [moq.pro: lite-07 on cluster dials](https://github.com/moq-dev/moq.pro/blob/main/quest/m2/lite07.md) - the mesh rollout that adopts the finalized version, and the customer rollout after it; moq.pro holds it in m2 until the cut is called
9 changes: 4 additions & 5 deletions quest/m1/qos/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,11 +31,10 @@ The counters and channels land here. Client health and preflight are
moq.pro (downstream) dashboard work, including the health badge and the
connection-health drill-down, consumes both.

Open, for the maintainer (the same question is recorded in
[client health](/quest/m1/stats/health.md)): whether anything computes a
per-broadcast verdict combining client reports, the relay's starvation, and
publisher timeliness, and where it would live. This line only reports the
counters.
The per-broadcast verdict combining client reports, the relay's starvation,
and publisher timeliness lives in moq.pro's
[health badge](https://github.com/moq-dev/moq.pro/blob/main/quest/m1/qos/badge.md).
This line only reports the counters.

Decided (2026-10-06 audit): [stats totals and prefix
tracks](/quest/m0/broadcast-epoch/stats-split.md) lands first, since it is m0
Expand Down
12 changes: 6 additions & 6 deletions quest/m1/stats/health.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,11 +53,10 @@ Guidance, to be settled while building:
- Lives beside the snapshot types in `hang` and `@moq/hang` unless building
it shows a better home.

Open, for the maintainer (the same question is recorded in
[QoS](/quest/m1/qos/README.md)): whether anything computes a per-broadcast
verdict combining client reports, the relay's starvation, and publisher
timeliness, and where it would live. Nothing here depends on the answer, and
no quest promises it until it is decided.
A per-broadcast verdict combining client reports, the relay's starvation,
and publisher timeliness lives in moq.pro's
[health badge](https://github.com/moq-dev/moq.pro/blob/main/quest/m1/qos/badge.md),
not here.

Prove a degrading publisher self-report, a degrading viewer report, a stale
report going unknown, and a counter reset by both a decrease and an epoch
Expand All @@ -72,6 +71,7 @@ Public API: new health types in `hang` and `@moq/hang`. Wire: none.
## Related

- [moq.pro: connection health](https://github.com/moq-dev/moq.pro/blob/main/quest/m2/qos-connection-health.md) - the per-project view built on this model
- [QoS](/quest/m1/qos/README.md) - the relay's delivery counters, which a combined verdict would also read (open above)
- [QoS](/quest/m1/qos/README.md) - the relay's delivery counters, which moq.pro's combined verdict also reads
- [moq.pro: health badge](https://github.com/moq-dev/moq.pro/blob/main/quest/m1/qos/badge.md) - the per-broadcast verdict combining this one with relay lag and publisher timeliness
- [Broadcast epochs](/quest/m0/broadcast-epoch/README.md) - a new epoch is one way a counter reset shows
- [TS health counters](/quest/m2/ts-health-stats.md) - container counters kept out of the verdict
5 changes: 5 additions & 0 deletions quest/m2/gpu-release.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,3 +26,8 @@ maintainer at release time:
- [Vulkan Video encode on AMD](/quest/m2/vulkan-encode.md) - the AMD encoder
- [VA-API encodes an external Vulkan image](/quest/m2/vaapi-vulkan-import.md) - the Intel proof
- [GPU capacity and health](/quest/m2/gpu-health.md) - keyed by the same device identity; moq.pro's admission still needs vendor code without it

## Related

- [moq.pro: Release multi-vendor GPU input upstream](https://github.com/moq-dev/moq.pro/blob/main/quest/m2/gpu-release.md) - tracks this release
- [moq.pro: Pin multi-vendor GPU input](https://github.com/moq-dev/moq.pro/blob/main/quest/m2/pronto-gpu-pin.md) - the Pronto bridge adopts it
Loading