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
1 change: 0 additions & 1 deletion quest/m0/test-flakes-2/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,6 @@ Public API: none. Wire: none.
- [dispatch-query's terminate test survives load](/quest/m0/test-flakes-2/dispatch-query-terminate.md) - `test_terminating_the_run_stops_the_running_phase` passes reliably under host load, re-enabled once fixed
- [Test PulseAudio servers stay off the desktop's D-Bus](/quest/m0/test-flakes-2/pulse-dbus.md) - concurrent media runs on one desktop never collide on `org.PulseAudio1`
- [The Python audio playout-delay test reads its frames](/quest/m0/test-flakes-2/audio-playout-delay.md) - `test_audio_consumer_reports_its_playout_delay` stops timing out on its first read in the merge queue
- [The dev host's locked-memory limit fits parallel sessions](/quest/m0/test-flakes-2/uring-memlock.md) - the maintainer's host raises the user's `RLIMIT_MEMLOCK`, which Node.js rings from parallel agent sessions fill before io_uring tests start
- [The FFI concurrent-ready test wakes both calls under load](/quest/m0/test-flakes-2/ffi-concurrent-ready.md) - `concurrent_ready_calls_all_wake` stops stalling its reader drain under load and is re-enabled
- [The datagram-end close test survives load](/quest/m0/test-flakes-2/datagram-end-close.md) - `a session close right after a datagram track's end keeps the end` stops aborting the track under load and is re-enabled
- [lite-05 copy fill checks idleness without wall time](/quest/m0/test-flakes-2/copy-fill-idle.md) - the copy-fill test proves no FETCH went out on the `Manual` clock, not a 200 ms real-time wait
Expand Down
54 changes: 0 additions & 54 deletions quest/m0/test-flakes-2/uring-memlock.md

This file was deleted.

1 change: 1 addition & 0 deletions quest/m1/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,7 @@ moves what remains of them once their claims merge.
- [The over-limit PUBLISH refusal invites a retry](/quest/m1/retry-interval-overload.md) - `EXCESSIVE_LOAD` sends the may-pass retry interval, not 0
- [A relay forwards an upstream refusal's retry interval](/quest/m1/retry-interval-forward.md) - a forwarded SUBSCRIBE refusal keeps the upstream's retry interval
- [Tests run on a mocked clock](/quest/m1/mock-clock-tests/README.md) - about 300 tests stop proving nothing happened by waiting, sleeping to settle, or asserting on elapsed time
- [moq-mux reads H.265 SPS without scuffle](/quest/m1/h265-sps-reader.md) - moq-mux's own SPS reader replaces scuffle-h265 and scuffle-expgolomb, and the fuzz regressions still pass

## Related

Expand Down
55 changes: 55 additions & 0 deletions quest/m1/h265-sps-reader.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
# [S] moq-mux reads H.265 SPS without scuffle

## Goal

moq-mux's `codec::h265` module parses the whole SPS with its own bounded
reader and returns the cropped size, VUI colour signal, and aspect ratio that
moq-mux and moq-video read today. scuffle-h265 and scuffle-expgolomb leave
the dependency tree. The committed `fmp4`, `annexb`, and `ts` fuzz
regressions and moq-video's SPS regression test still pass.

## Plan

Decided 2026-11-07 (maintainer, /quest-unblock): ✅ drop scuffle-h265 and
make the parser a module in moq-mux. ScuffleCloud/scuffle looks unmaintained
(last commit to main 2025-10-31; scuffle-h265 0.2.2 and scuffle-expgolomb
0.1.5 are from mid-2025; outside PRs such as
[ScuffleCloud/scuffle#652](https://github.com/ScuffleCloud/scuffle/pull/652)
sit unreviewed), and
[ScuffleCloud/scuffle#653](https://github.com/ScuffleCloud/scuffle/issues/653)
and [#654](https://github.com/ScuffleCloud/scuffle/issues/654) have no reply.
Not chosen: fork scuffle under moq-dev and publish patched crates; keep
waiting on upstream releases. Milestone: ✅ m1 (not chosen: m2, m4 as before).

moq-mux already walks every SPS field itself before handing it to scuffle
(`sps::check` and `walk` in `rs/moq-mux/src/codec/h265/sps.rs`, added by
[moq-dev/moq#7685](https://github.com/moq-dev/moq/pull/7685)), so turn that
walk into the parser:

- Read the fields the callers use instead of only bounding them, in the
spec's layout (ITU-T H.265 7.3.2.2.1). Drop the places where the walk copies
scuffle 0.2.2's non-spec layout, such as `sub_layer_level_idc` read twice
and `iv_di_mc_enabled_flag` read once.
- Keep the head fallback for SPSs whose later fields break a semantic
constraint real encoders violate (`matrix_coeffs` 0 on 4:2:0), and keep
refusing truncated or out-of-range values.
- Replace the scuffle `NALUnitType`, `Profile`, `AspectRatioInfo`, and
`VideoSignalType` uses in moq-mux (`h265/`, `container/ts/video_timing.rs`,
`container/mkv/hvcc.rs`) and moq-video (`decode/vui.rs`) with moq-mux's own
types, crate-private where moq-video doesn't need them.
- Keep every regression input, including the `scuffle-h265-*` and
`scuffle-expgolomb` ones moq-video's tests include.

scuffle-av1 stays, though it is the same upstream: its one known bug, a
UVLC leading-zero count that overflows a `u8`, is guarded at moq-mux's own
boundary (`validate_timing` in `rs/moq-mux/src/codec/av1/import.rs`, from
[moq-dev/moq#8042](https://github.com/moq-dev/moq/pull/8042)). Keep that
guard while scuffle-av1 is a dependency.

Public API: none; moq-mux exports no scuffle type.
Wire: none.

## Related

- [Media fuzz findings](/quest/m1/fuzz-findings/README.md) - found the scuffle overflows
- [Re-run the SPS fuzzer on h264-reader](/quest/m4/sps-fuzz-h264-reader.md) - the H.264 half
25 changes: 20 additions & 5 deletions quest/m3/video-quality/corpus-bucket.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,16 +9,31 @@ public access exposes a whole bucket and a prefix cannot be private behind
it. A read-only token for the private bucket is a secret the nightly
video-quality jobs can read.

This waits on a Cloudflare account action. Check it by fetching one public
object anonymously, one private object with the secret from a nightly
`workflow_dispatch` run, and the same private object anonymously, which must
fail. Delete this quest once all three hold.

## Plan

Decided 2026-11-07 (maintainer, /quest-unblock): ✅ a checked-in wrangler
setup creates the buckets. Not chosen: running the wrangler commands once by
hand with nothing checked in; leaving it all to the maintainer.

- Add a `just create` recipe under `infra/`, the way `infra/nix/justfile`
creates the nix.moq.dev buckets: both buckets, with public access and a
moq.dev custom domain (such as `corpus.moq.dev`) on the open one only.
Run it with the desktop's existing `wrangler login`; wrangler there reaches
the Cloudflare account.
- Follow the existing R2 secret naming (`MBX_R2_*`, `R2_*`), with a separate
token that is read-only and scoped to the private bucket. The corpus must
never share write credentials with the caches.
- Upload is a maintainer action. The manifest the harness owns records each
object's sha256, so a replaced object fails the run instead of silently
changing the baseline.

## Waiting

- Maintainer: once the setup has created the private bucket, mint its
read-only token in the dashboard (R2, Manage API tokens, Object Read only,
scoped to that bucket) and store it with `gh secret set` under the names
the setup documents. Wrangler cannot create R2 API tokens, and an agent
never handles the secret. Check by fetching one public object anonymously,
one private object with the secret from a nightly `workflow_dispatch` run,
and the same private object anonymously, which must fail. Delete this quest
once all three hold.
1 change: 0 additions & 1 deletion quest/m4/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,6 @@ deleted.
- [moq-bench reports sub-millisecond latency](/quest/m4/bench-latency-resolution.md) - steady-window latency resolves finer than 1 ms
- [Benchmark series stay meaningful](/quest/m4/bench-hygiene.md) - a warm `burst` variant, stale series pruned, and slow-group `bytes` kept out of series names
- [Re-run the SPS fuzzer on h264-reader](/quest/m4/sps-fuzz-h264-reader.md) - the H.264 SPS overflow is rechecked on the new parser
- [Drop the H.265 SPS pre-walk once scuffle is fixed](/quest/m4/scuffle-sps-bump.md) - waiting on ScuffleCloud/scuffle#653 and #654 releases, then bump and drop the walk
- [PCM encodes in one pass](/quest/m4/pcm-bulk-encode.md) - the PCM encoder converts a frame in bulk instead of one sample at a time
- [moq-quic's internal dev-dependencies are path-only](/quest/m4/quic-dev-dep-path.md) - moq-congestion is a path dev-dependency
- [moq-mux's AAC config reports SBR](/quest/m4/aac-sbr-config.md) - moq-audio reads backward-compatible SBR from the config
Expand Down
39 changes: 0 additions & 39 deletions quest/m4/scuffle-sps-bump.md

This file was deleted.

13 changes: 9 additions & 4 deletions quest/m5/rind-instant-acme.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,13 +3,18 @@
## Goal

`rind-instant-acme` is on crates.io, built on a published instant-acme 0.9.
It holds once moq-dev/rind's
[Publish rind-instant-acme](https://github.com/moq-dev/rind/blob/main/quest/m3/instant-acme-publish.md)
quest is deleted and `cargo search rind-instant-acme` shows it. This quest
only waits; delete it once that holds.
This quest only waits; delete it once that holds.

## Plan

rind's adapter waits on instant-acme's 0.9 release, which carries the
pluggable `CryptoProvider`. Only [relay ACME](/quest/m5/relay-acme.md) needs
it (maintainer, 2026-10-31).

## Waiting

- moq-dev/rind: its
[Publish rind-instant-acme](https://github.com/moq-dev/rind/blob/main/quest/m3/instant-acme-publish.md)
quest is deleted and `cargo search rind-instant-acme` shows the crate.
Checked 2026-11-07: the rind quest is still open, crates.io has no
`rind-instant-acme`, and instant-acme's latest is 0.8.5.
Loading