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
12 changes: 6 additions & 6 deletions quest/m1/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,8 +63,9 @@ padding and the browser's rung disable stay in m2, with only padding's
lite-07 stream type here.

Added 2026-10-22 (maintainer, clustering audit): three interim fixes for
announce churn on today's hop-list mesh, each backported to `release`, so
deployments get relief before the route layer ships; and stats groups as
announce churn on today's hop-list mesh, shipping with the next cut from
`main` (not backported to `release`), so deployments get relief before the
route layer ships; and stats groups as
tracks, so per-group stats stop costing cluster announces.

## Required
Expand All @@ -74,9 +75,9 @@ tracks, so per-group stats stop costing cluster announces.
- [Readers follow restarts](/quest/m1/sink-restart-follow.md) - every moq-cli and moq-gst reader, moqsrc and `moq play` included, follows instances through `announced_broadcast` and an epochless `Restart` where its output can mark it; otherwise it stays on the old instance and fails once that route dies
- [In-band auth](/quest/m1/auth/README.md) - a session tells its peer what it may publish and subscribe to, unions tokens presented in band, and fails loud on an out-of-scope publish
- [Cluster routing](/quest/m1/cluster-routing/README.md) - prove shared routing contracts, implement per-origin routes, and connect outbound local clusters
- [Announce cursors stay linear](/quest/m1/announce-cursor-cpu.md) - a withdrawal costs each announce cursor O(K log K), and a no-op route change allocates nothing; backported to `release`
- [Path length setting](/quest/m1/max-hops-setting.md) - operators cap hop paths near their mesh diameter instead of 32; backported to `release`
- [Draining relays don't pull peers back](/quest/m1/drain-peer-redial.md) - cluster peers fail over instead of redialing a draining relay, and peer redials back off with jitter; backported to `release`
- [Announce cursors stay linear](/quest/m1/announce-cursor-cpu.md) - a withdrawal costs each announce cursor O(K log K), and a no-op route change allocates nothing
- [Path length setting](/quest/m1/max-hops-setting.md) - operators cap hop paths near their mesh diameter instead of 32
- [Draining relays don't pull peers back](/quest/m1/drain-peer-redial.md) - cluster peers fail over instead of redialing a draining relay, and peer redials back off with jitter
- [Stats groups as tracks](/quest/m1/stats-group-tracks.md) - one stable node broadcast per stats producer, with each group a produced track listed by TRACKS
- [Routing guide](/quest/m1/routing-guide.md) - concepts and practical outbound federation setup
- [Controlled time](/quest/m1/time/README.md) - every crate and package reads time through moq-clock or @moq/clock, with regression tests for the changed contracts
Expand Down Expand Up @@ -112,7 +113,6 @@ tracks, so per-group stats stop costing cluster announces.
- [Audio jitter target](/quest/m1/audio-jitter-target/README.md) - the playout target is default in both languages; a manual browser proof and a native trace replay remain
- [Buffered backpressure timestamps](/quest/m1/audio-backpressure-timestamps.md) - buffered audio keeps holding frames past 2^31 microseconds instead of decoding ahead and dropping audio
- [Audio playout memory](/quest/m1/audio-playout-memory.md) - a catalog's advertised jitter or delay cannot size decoded PCM; the lookahead stays encoded
- [Jitter estimator density](/quest/m1/jitter-density.md) - the estimator does O(1) work per frame however densely timestamps are packed, in JS and Rust
- [AAC alias classification](/quest/m1/aac-he-alias.md) - every accepted AAC spelling gets the right frame duration from one classification
- [A/V clock](/quest/m1/av-clock.md) - the audio playhead drives Sync.reference while audio plays, through per-track sync handles
- [Publish channel count](/quest/m1/publish-audio-channel-count.md) - forcing a channel count on an Audio.Capture stops costing the subscriber gaps of silence, and the media fixture's cold-start audio-tone flake is fixed at its cause
Expand Down
8 changes: 4 additions & 4 deletions quest/m1/announce-cursor-cpu.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,9 @@ An announce cursor's work per event is independent of how many entries it
holds back. When an origin holding K broadcasts goes away, each cursor does
O(K log K) work, not O(K²). A route change that leaves a cursor's winning
route unchanged allocates nothing for that cursor. Both properties have an
operation-count regression test and a benchmark, and the fix is backported
to `release`.
operation-count regression test and a benchmark. It ships with the next cut
from `main`; the maintainer decided on 2026-10-22 not to backport it to
`release`.

## Plan

Expand Down Expand Up @@ -44,8 +45,7 @@ both fan-out axes: one origin withdrawing 1k and 10k broadcasts, and one
broadcast's route churning, each under 1, 20, and 100 cursors, against `main`
before the change.

Backport: per CONTRIBUTING, land on `main`, then port onto `release` as a
separate PR keeping the published API. No wire change, no public API change.
No wire change, no public API change.

## Related

Expand Down
1 change: 0 additions & 1 deletion quest/m1/audio-playout-memory.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,4 +48,3 @@ any `js/watch` API change goes in its `MIGRATE.md`.

- [Buffered backpressure timestamps](/quest/m1/audio-backpressure-timestamps.md) - the 32-bit truncation in the same `Backpressure`, landing first
- [Audio jitter target](/quest/m1/audio-jitter-target/README.md) - the playout target this sizes memory for
- [Jitter estimator density](/quest/m1/jitter-density.md) - the CPU side of the same hostile-publisher concern
4 changes: 2 additions & 2 deletions quest/m1/drain-peer-redial.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,8 @@ When a clustered relay drains, its cluster peers fail over to other routes
instead of redialing it, and they reconnect once its replacement is up. Peer
redials back off with jitter and a cap of tens of seconds, so a mesh
recovering from an outage doesn't redial in lockstep and a recovered peer
is not left waiting minutes. Fixed on `main` and backported to `release`.
is not left waiting minutes. It ships with the next cut from `main`; the
maintainer decided on 2026-10-22 not to backport it to `release`.

## Plan

Expand Down Expand Up @@ -39,7 +40,6 @@ relay while it drains, and one reconnect after it restarts. Backoff tests
assert spread and cap under controlled time.

Public API: none expected; report any connect config change. Wire: none.
Backport onto `release` as a separate PR.

## Related

Expand Down
42 changes: 0 additions & 42 deletions quest/m1/jitter-density.md

This file was deleted.

5 changes: 3 additions & 2 deletions quest/m1/max-hops-setting.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,8 @@
A relay operator can set the longest hop path a relay accepts or forwards,
with today's 32 as the default. On a mesh whose diameter is a few hops, a
cap near diameter plus a margin stops lite-06 path hunting from exploring
long detours after a withdrawal. The setting is backported to `release`.
long detours after a withdrawal. It ships with the next cut from `main`; the
maintainer decided on 2026-10-22 not to backport it to `release`.

## Plan

Expand Down Expand Up @@ -33,7 +34,7 @@ the residual counterexamples' final state. A path longer than the cap is
dropped on receive and never sent.

Docs: `doc/bin/relay/cluster.md` gains the setting. Public API: one relay
config field. Wire: none. Backport onto `release` as a separate PR.
config field. Wire: none.

## Related

Expand Down
2 changes: 1 addition & 1 deletion quest/m1/release-audit/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ network-impairment performance result is implied by these checks.

## Required

The 21 children comprise 17 reproduced or source-confirmed findings, three
The children comprise reproduced or source-confirmed findings,
contract/lifetime investigations, and one security-review pointer. Each
child records whether its behavior is new on main or inherited from release.

Expand Down
Loading