Skip to content
1 change: 1 addition & 0 deletions quest/m0/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,7 @@ since cutting segments from first-frame pts waits on nothing in m1.
- [Backport audio groupDuration](/quest/m0/backport-audio-group-duration.md) - `@moq/publish` 0.5.4 on `release` can pack several Opus frames per group, making Cloudflare's relay drop audio less often
- [Backport the SETUP-path and iroh-key fixes](/quest/m0/backport-security-fixes.md) - `release` refuses a conflicting SETUP Path and keeps persisted iroh keys private, in one patch release
- [Backport the joined-head FETCH race fix](/quest/m0/backport-fill-head-race.md) - a `release` relay stops FETCHing a group head its own SUBSCRIBE is bringing, which left live readers hanging
- [Release resumes owed groups or proves it doesn't need to](/quest/m0/backport-resume-owed-groups.md) - after main's resume fix, reproduce its cases on `release`, then backport or delete
- [CI cost and latency](/quest/m0/ci/README.md) - cloud CI runs only in a batched merge gate as one `just ci` pass per batch, expensive checks run nightly and gate `release`, caches move to R2, and runners are chosen last
- [More tests under load](/quest/m0/test-flakes-2/README.md) - load-only and queue failures, one quest per flake, fixed at the cause, since each one fails a whole batch
- [A waiter's record limit changes no behavior](/quest/m0/kio-waiter-records.md) - two moq-net tests stop failing when kio's waiters remember 16 lists, and the limit becomes a tuning knob worth 3.9% per delivered group
Expand Down
35 changes: 35 additions & 0 deletions quest/m0/backport-resume-owed-groups.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# [S] Release resumes owed groups or proves it doesn't need to

## Goal

A `release` relay's resumed read gets every owed group or a drop for it,
never a hang, if `release` has the hang. Otherwise, this quest records the
evidence that `release` isn't exposed and is deleted.

## Plan

Decided 2026-11-03 (maintainer, /quest-plan of the follow-ups from
[moq-dev/moq#7708](https://github.com/moq-dev/moq/pull/7708)): milestone m0,
beside the other backports. It started once #7708, the resume fix on main
that this ports, merged.

- Exposure is unproven. `origin/release` (moq-net 0.3.19 at `acf91a00b9`)
has no `live_floor`, `judge`, or `Misses`. The shared live floor that
#7708 fixes arrived with
[moq-dev/moq#4741](https://github.com/moq-dev/moq/pull/4741), which is not
on `release`. `release` does have `resume.rs`, so
the symptom may still come through another path.
`release` also speaks draft 22 (`rs/moq-net/src/ietf/version.rs`), so
check drafts 14 to 22.
- Reproduce first. Port #7708's regression tests (the cache-loss case and
the bounded resumes) onto `release`'s older cache model and run them
there. If none fails, delete this quest and record the run in the PR.
- If one fails, fix it on `release` with the smallest change that matches
main's contract. Expect a hand-port, not a cherry-pick, since the cache
models differ. Then cut a patch release under the release line's usual
rules. Bump the version by hand at the semver level the change needs.
- Keep it separate from [the joined-head FETCH backport](/quest/m0/backport-fill-head-race.md).
#7708 says the PUBLISH_DONE grace correction tracked there is a separate
fix.

Public API: none expected. Wire: none.
2 changes: 2 additions & 0 deletions quest/m0/ci/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -166,3 +166,5 @@ The historical samples locate candidates; they are not controlled benchmarks.
- [moq-audio's default-feature test build is clippy-clean and gated](/quest/m0/ci/default-feature-test-lint.md) - the dead `retains`/`fail` under default-feature `--tests` clippy is fixed, and the gate catches it next time
- [A release merge opens no stale release PR](/quest/m0/ci/release-pr-after-release.md) - `just rs release` publishes before it proposes, so a merged release isn't re-proposed
- [Dependabot leaves the workspace-hack to hakari](/quest/m0/ci/dependabot-workspace-hack.md) - cargo group PRs stop hand-editing `rs/workspace-hack/Cargo.toml`
- [mbx's free-space GC never removes a live target](/quest/m0/ci/mbx-gc.md) - the cargo shim stops deleting targets other sessions use when the host disk runs low
- [Bun runs only the test files we name](/quest/m0/ci/bun-test-paths.md) - scripted `bun test` calls pass exact paths, so generated copies never run
31 changes: 31 additions & 0 deletions quest/m0/ci/bun-test-paths.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
# [XS] Bun runs only the test files we name

## Goal

Every scripted `bun test <file>` passes an exact path. Bun then never runs a
same-named copy elsewhere in the checkout, such as a generated release tree
under `target/` or a scratch directory. A check keeps new bare filters
from coming back.

## Plan

Decided 2026-11-03 (maintainer, /quest-plan of the follow-ups from
[moq-dev/moq#7680](https://github.com/moq-dev/moq/pull/7680), first seen in
[moq-dev/moq#7669](https://github.com/moq-dev/moq/pull/7669)): milestone m0,
in the CI epic.

- Cause: bun treats a bare argument as a substring filter over discovered
files. Only arguments that start with `./` or `/` are exact. The API
checker's generated release tree under the build cache held copies of
`sh/gh/*.test.ts`, and those old tests ran against main's workflows.
- Bare filters on main: `.github/justfile:30,54,59`
(`sh/gh/alert|setup|ffi|cpp|publish.test.ts`),
`test/json-properties.sh:12`, `test/resume-model.sh:12`,
`test/justfile:52,54,277` (check what the harness lists expand to), and
`test/smoke/justfile:122`. Prefix each with `./`.
- Guard: have the test inventory (`sh/gh/test-inventory.py`) or a small
lint refuse a scripted `bun test` argument that ends in `.test.ts` and
lacks `./` or `/`. If no root `bunfig.toml` exists, also consider one
that limits discovery to the source roots.

Public API: none. Wire: none.
47 changes: 47 additions & 0 deletions quest/m0/ci/mbx-gc.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
# [S] mbx's free-space GC never removes a live target

## Goal

On agent hosts, a cargo call through the mbx shim never deletes a Cargo
target another session is still using. A run that loses disk headroom gets
a clear failure instead of silently evicting the shared cache. The host
settings that keep it so live in `kixelated/dotfiles`.

## Plan

Decided 2026-11-03 (maintainer, /quest-plan of the follow-ups from
[moq-dev/moq#7742](https://github.com/moq-dev/moq/pull/7742)): milestone m0,
in the CI epic.
[moq-dev/moq#7715](https://github.com/moq-dev/moq/pull/7715) only worked
around the same GC for long interop runs.

- Incident
([comment](https://github.com/moq-dev/moq/pull/7742#issuecomment-6605544835)):
`mbx[gc]: 11.2 GiB free … under the 50.0 GiB minimum`, then "removed 7
target directories (… 6 abandoned and 1 live)". It also evicted about
30 GiB of shared cache objects below `gc.max_size`, because the disk was
under `gc.min_free_size`.
- This is documented mbx behaviour (`mbx gc --help`): below
`gc.min_free_size`, it collects past its budgets, managed targets first.
`~/work/dotfiles/mbx/config.toml` sets no `[gc]` options, so the
defaults apply. On 2026-11-03, `/` on `desktop` was 98% full with 49 GB
free, still under the threshold, so any cargo call can trigger it again.
- Work out why the disk is that full first: other worktrees' targets, `.tmp/`
scratch, Nix store. `quest worktree` reclaims finished checkouts.
- Then protect live targets in dotfiles. Lowering `min_free_size` only
changes when collection runs: below it, mbx still removes unprotected
managed targets. mbx's docs
([managed targets](https://mr-boxington.jdx.dev/managed-targets)) describe
a running command's lease and a `target.keep` setting. Check which of them
failed for the target logged as live: a binary run straight from
`target/` holds no lease. Then set `target.keep` or the fitting `[gc]`
option. If mbx can't spare live targets at all, report that upstream and
record the issue link here.
- Edit dotfiles in place (`~/work/dotfiles` is live config), and link its
commit here when done.

Public API: none. Wire: none.

## Related

- The queue host keeps the queue's disk - disk policy for the queue host, configured in kixelated/nixos
6 changes: 5 additions & 1 deletion quest/m0/interop-green/README.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# [XS] Interop and Video pass on main
# Interop and Video pass on main

## Goal

Expand Down Expand Up @@ -65,3 +65,7 @@ The P2P data-channel test timed out once, in 41668668824, and passes
locally; triage it if it recurs.

Public API: none. Wire: none.

## Required

- [The open-GOP recovery fixture provides the broadcast name](/quest/m0/interop-green/open-gop-fixture.md) - the open-GOP browser fixture stubs `in.name`, and an exception in an effect fails the test at once instead of timing out
36 changes: 36 additions & 0 deletions quest/m0/interop-green/open-gop-fixture.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
# [XS] The open-GOP recovery fixture provides the broadcast name

## Goal

The scheduled Interop run's "Harness regressions" step passes the
`open-gop.browser.ts` case "software video recovery trims orphan pictures
after join and later gap". The fixture's fake broadcast provides everything
`@moq/watch`'s decoder reads. From now on, an exception thrown inside a
fixture's effect fails the test immediately with that error, instead of
surfacing as a 60-second timeout.

## Plan

Decided 2026-11-03 (maintainer, /quest-plan of the follow-ups from
[moq-dev/moq#7715](https://github.com/moq-dev/moq/pull/7715) and
[moq-dev/moq#7716](https://github.com/moq-dev/moq/pull/7716)): milestone m0,
a child of the Interop epic, since it breaks the scheduled run.

- Cause: [moq-dev/moq#7222](https://github.com/moq-dev/moq/pull/7222)
(`2738588cfc`) made `js/watch/src/video/decoder.ts` read
`broadcast.in.name.peek()` for stats. The fake broadcast in
`test/interop/clients/js/open-gop/main.ts` provides only `out: { catalog,
active }` and `relativeBroadcast`, so the read throws inside an effect.
The scheduled run
[41668668824](https://github.com/moq-dev/moq/actions/runs/41668668824)
fails with `TypeError: Cannot read properties of undefined (reading
'name')` at `window.runRecovery`.
- Add `in: { name }` to the stub, typed against the real broadcast's shape
where the fixture allows it, so the next field the decoder reads fails
type-checking instead of at run time.
- Fail fast: route page errors and effect exceptions to a test failure.
[moq-dev/moq#7716](https://github.com/moq-dev/moq/pull/7716) adds
page-error collection to `harness.browser.ts`. Reuse it if it has landed,
or add the same collection here and let #7716 merge onto it.

Public API: none. Wire: none.
9 changes: 8 additions & 1 deletion quest/m0/nightly/README.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# [S] Nightly passes on main
# Nightly passes on main

## Goal

Expand Down Expand Up @@ -32,3 +32,10 @@ This README's own work, after the children:
threshold to [bench CI](/quest/m1/bench-ci.md).

Public API: none. Wire: none.

## Required

- [Nightly's Rust and JS audits pass](/quest/m0/nightly/audits.md) - RUSTSEC-2026-0173 and the root `bun.lock` glob and minimatch advisories are upgraded away or ignored with a reason
- [moq-net's ingest fuzz target finds no stall](/quest/m0/nightly/ingest-fuzz.md) - the 13-byte stream that stalls ingest is fixed at its cause and kept as a regression test
- [Nightly's shipping-size check passes](/quest/m0/nightly/shipping-size.md) - js/net, js/watch, and moq-relay growth over 5% is traced to its commits, then shrunk or accepted
- [Nightly's Miri job stays inside its time budget](/quest/m0/nightly/miri.md) - Miri gets `rust-src`, then finishes inside its 60-minute job and 15-minute-per-test budgets
39 changes: 39 additions & 0 deletions quest/m0/nightly/audits.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
# [XS] Nightly's Rust and JS audits pass

## Goal

Nightly's Rust and JS audit jobs pass on `main`. Each current advisory is
fixed by an upgrade, or by an override or an ignore that names the advisory
and its reason, so a new advisory shows up as the only red.

## Plan

Decided 2026-11-03 (maintainer, /quest-plan of the follow-ups from
[moq-dev/moq#7667](https://github.com/moq-dev/moq/pull/7667)): milestone m0,
a child of the Nightly epic.

Both fail in the scheduled run of 2026-11-03
([run 41656613559](https://github.com/moq-dev/moq/actions/runs/41656613559)):

- **Rust**
([job](https://github.com/moq-dev/moq/actions/runs/41656613559/job/125988511066)):
RUSTSEC-2026-0173, `proc-macro-error2` unmaintained, reached through
`hax-lib-macros`. Find which of our crates pulls `hax-lib` in. Upgrade it
if a release drops the edge. Otherwise ignore the advisory in the audit
config with a comment naming the parent crate, since an unmaintained
proc-macro crate runs only at build time.
- **JS**
([job](https://github.com/moq-dev/moq/actions/runs/41656613559/job/125988512588)):
the root `bun.lock` resolves `glob` (GHSA-3g3m-2fjr-6pw4) and `minimatch`
(GHSA-g3hv-75wg-m249) to vulnerable versions. Raise them through the parent
that pins them, or with a root `overrides` entry.

Keep [the dependency audit](/quest/m2/audit-deps.md) in sync. It already
records that the root lock is not clean, so update its notes once this
lands.

Public API: none. Wire: none.

## Related

- [Dependency audit](/quest/m2/audit-deps.md) - the recurring audit that owns advisory policy
35 changes: 35 additions & 0 deletions quest/m0/nightly/ingest-fuzz.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# [S] moq-net's ingest fuzz target finds no stall

## Goal

Nightly's moq-net `ingest` fuzz target runs its budget without a finding.
The stall it found on a complete 13-byte stream is fixed at its cause, and
that input is kept as a regression test.

## Plan

Decided 2026-11-03 (maintainer, /quest-plan of the follow-ups from
[moq-dev/moq#7667](https://github.com/moq-dev/moq/pull/7667)): milestone m0,
a child of the Nightly epic.

- The scheduled run of 2026-11-03
([job](https://github.com/moq-dev/moq/actions/runs/41656613559/job/125988510475))
panicked at `rs/moq-net/src/fuzz/ingest.rs:298` with "the ingest stalled
on a complete 13-byte stream". Its crash artifact is `crash-106ef498…`.
The 2026-11-01 E0391 build failure noted in
[the CI audit](/quest/m2/audit-ci.md) no longer occurs.
- Download the artifact before it expires, then replay it with
`cargo fuzz run ingest <artifact>`. Decide whether the ingest really
stalls on that input or the harness's stall check is wrong, and fix
whichever it is.
- Add the input as a fixed regression test next to the target, so `just
check` covers it without fuzzing.
- The same run's `Fuzz (ts)` and `Fuzz (annexb)` failures are media
targets. They belong to [fuzz findings](/quest/m1/fuzz-findings/README.md),
or else to the Nightly epic's own triage, not to this quest.

Public API: none expected. Wire: none expected.

## Related

- [Fuzz findings](/quest/m1/fuzz-findings/README.md) - the media fuzz targets' findings
6 changes: 6 additions & 0 deletions quest/m2/miri-nightly-budget.md → quest/m0/nightly/miri.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,12 @@ Decided 2026-10-31 (user, /quest-plan of the follow-ups from the 2026-10-31 /que
(merged), which finished the Miri for in-memory unsafe quest.
Milestone m2 (user: "use recommended for any CI/flakes").

Decided 2026-11-03 (maintainer, /quest-plan of the follow-ups from [moq-dev/moq#7667](https://github.com/moq-dev/moq/pull/7667)):
moved from m2 under [Nightly passes on main](/quest/m0/nightly/README.md),
since the missing `rust-src` keeps the m0 Nightly red. The scheduled run of
2026-11-03 ([run 41656613559](https://github.com/moq-dev/moq/actions/runs/41656613559/job/125988511062))
still fails the same way.

Act on the first Nightly runs' timings, not ahead of them. Locally (24
cores) `just rs miri` took 11.5 min wall: strict pass 118 tests in 109 s,
epoch pass 94 in 307 s.
Expand Down
39 changes: 39 additions & 0 deletions quest/m0/nightly/shipping-size.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
# [S] Nightly's shipping-size check passes

## Goal

Nightly's shipping-size check passes on `main`. Every growth over its 5%
threshold is traced to the commits that caused it. Each is then shrunk back,
or accepted as a new baseline with the reason recorded.

## Plan

Decided 2026-11-03 (maintainer, /quest-plan of the follow-ups from
[moq-dev/moq#7667](https://github.com/moq-dev/moq/pull/7667)): milestone m0,
a child of the Nightly epic.

The scheduled run of 2026-11-03
([job](https://github.com/moq-dev/moq/actions/runs/41656613559/job/126039954216))
failed on growth since the previous run:

- `js/net` raw went from 444,692 to 467,348 bytes.
- `js/watch` also grew past the threshold.
- All four moq-relay archives grew to about 10.2–11.3 MB, from about
9.5–10.3 MB.

Bisect each artifact between the two runs' commits. Likely suspects are the
recent bigint group IDs ([moq-dev/moq#7681](https://github.com/moq-dev/moq/pull/7681))
for js/net, and any new default feature or dependency for moq-relay.
`cargo bloat` and the bundle's metafile name the code that grew.

If the threshold compares only against the previous run, one intended jump
fails every night until the baseline moves. Check how the job sets its
baseline, and give it a documented way to accept a reviewed growth.
[Size audit](/quest/m2/audit-size.md) owns the release-time view of these
sizes.

Public API: none. Wire: none.

## Related

- [Size audit](/quest/m2/audit-size.md) - pre-cut size investigation and the post-release refresh
4 changes: 4 additions & 0 deletions quest/m0/test-flakes-2/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -95,3 +95,7 @@ Public API: none. Wire: none.
- [The JS worklet library-build test survives load](/quest/m0/test-flakes-2/js-worklet-build.md) - the lazy-blob worklet build test stops timing out at bun's 5 seconds
- [moq-archive's cross-backend recording test survives load](/quest/m0/test-flakes-2/archive-backends-identical.md) - `recordings_are_byte_identical_on_every_backend` stops splitting S3's video objects differently
- [moq-ffi's panicked-origin supervision test survives load](/quest/m0/test-flakes-2/ffi-origin-panic.md) - a read the origin driver's panic ends always reports `MoqError::Task`
- [The scheduled macOS WebSocket version test completes reliably](/quest/m0/test-flakes-2/macos-websocket.md) - fix the scheduled timeout while preserving newest-version negotiation assertions
- [@moq/net's lite subscribe tests wait for the whole request](/quest/m0/test-flakes-2/js-subscribe-fixture.md) - the three lite subscribe-with-track cases pass under forced yields
- [Concurrent PulseAudio harness runs don't share a D-Bus name](/quest/m0/test-flakes-2/pulse-dbus.md) - parallel media runs no longer collide on `org.PulseAudio1`
- [@moq/net's uni-stream flood test survives reruns](/quest/m0/test-flakes-2/js-stream-flood.md) - "a flood of uni streams yields" passes under `--rerun-each` and load
18 changes: 16 additions & 2 deletions quest/m0/test-flakes-2/ietf22-fallback.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,8 @@
## Goal

When the newest of two live publishers withdraws, a browser `@moq/watch`
viewer on moq-transport-22 plays the still-live older run within the media
lane's derived 1039 ms bound. It keeps its session, and its audio resumes
viewer on moq-transport-22, or on moq-lite in Firefox, plays the still-live
older run within the media lane's derived 1039 ms bound. It keeps its session, and its audio resumes
with its video. Both failures are fixed at their cause once one recurs with
enough evidence to reproduce it deterministically.

Expand All @@ -21,6 +21,20 @@ enough evidence to reproduce it deterministically.
Neither failure has a known cause or a reproduction yet, so no production or
test change is justified until one recurs.

Recurrence, added 2026-11-03 (maintainer, /quest-plan of the follow-ups from
[moq-dev/moq#7667](https://github.com/moq-dev/moq/pull/7667)): Nightly's
Firefox media job failed `live incumbent fallback plays` on two consecutive
nights with the audio-stall symptom (`audioStalled:true, audioTimestamp:0`
after the fallback), on `old-moq-lite-07-wip`:
[2026-11-02](https://github.com/moq-dev/moq/actions/runs/41483654426/job/125408204778)
and
[2026-11-03](https://github.com/moq-dev/moq/actions/runs/41656613559/job/125988510133).
[moq-dev/moq#7716](https://github.com/moq-dev/moq/pull/7716) found it
separate from the Firefox tone problem. Read those jobs' artifacts first. If
they isolate the cause, the Waiting item clears. If they don't, rerun the
Waiting section's command with `--media-engines firefox` and the same
`RUST_LOG` filter.

Two failures were seen while landing
[moq-dev/moq#6548](https://github.com/moq-dev/moq/pull/6548), on a host at
load average 30 to 70:
Expand Down
Loading
Loading