Skip to content

test(net): settle refresh as a soft trigger - #6437

Merged
kixelated merged 6 commits into
mainfrom
quest/m1/refresh/README
Oct 23, 2026
Merged

kixelated merged 6 commits into
mainfrom
quest/m1/refresh/README

Conversation

@kixelated

@kixelated kixelated commented Oct 23, 2026 •

Copy link
Copy Markdown
Collaborator

Problem

Refresh demand and moq-json's answer already worked, but their integration through relays was not covered, and the refresh quest promised that a late joiner downloads about R + 1 snapshots' worth. Delivery never kept that promise: a join over the ratio receives the cached group while the fresh one is requested upstream. With R = 1, a 14-byte snapshot and 64 deltas, a reader beyond two relays can read all 517 cached bytes before the JSON owner answers.

Approach

Settle refresh as a soft trigger, which Rust and JS already implement: a live join over the ratio keeps receiving the cached group and asks for a fresh one. No serving behavior changes.

  • A normal CI integration test runs the real moq-json snapshot Producer and Consumer over the simulated harness: publisher, relay A, relay B, reader. It checks ratios 1 and 2 below, at, and above the threshold; 60 simulated seconds without a join; demand answered once; the late reader receiving the whole cached group first, then a complete snapshot in group 1 at the newest source timestamp; and later deltas for existing and new readers.
  • The Rust and JS unit tests for a join over the ratio now also assert the joiner receives the cached group.
  • The API docs (track::Info::refresh, JS Info.refresh, moq_json::snapshot, moq-c, Python) drop the claim that a joiner never downloads much more than a snapshot. The lite draft states that the request does not hold back delivery. doc/concept/moq-lite.md gains a Refresh section.
  • The refresh quest is finished and deleted, with its links.

Impact

  • No public API, wire-format, or serving behavior change; no migration.
  • Draft text only: TRACK_INFO Refresh now says a pending request does not hold back cached delivery.
  • Consumer: moq-json's snapshot producer/consumer through clustered relay forwarding.

Decisions

The maintainer chose a soft trigger over withholding an oversized cached prefix. The ratio limits how often groups roll, not what a joiner downloads; the R + 1 download claim is dropped.

Alternatives

Withholding the cached prefix for an oversized join would keep the byte bound, but needs terminal behavior when the source finishes, aborts, or cannot answer, and per-reader handling of cold caches, late track info, and route-copy replacement in both Rust and JS. Rejected for that cost.

Follow-ups

None.

(Written by Claude Opus 5.5)

🤖 Generated with Claude Code

kixelated and others added 2 commits October 22, 2026 18:39
Quest-Claim: cf41f64c56e31f1e
Co-Authored-By: GPT-6 <codex@openai.com>
@kixelated kixelated changed the title Refresh: new groups on demand test(json): cover refresh through a two-relay cluster Oct 23, 2026
kixelated and others added 2 commits October 22, 2026 22:25
A live join over the refresh ratio keeps receiving the cached group while
the fresh one is requested. Pin that in the Rust and JS unit tests and the
two-relay JSON integration test, drop the byte-bound claims from the API
docs and bindings, state it in the lite draft, and finish the refresh quest.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kixelated
kixelated marked this pull request as ready for review October 23, 2026 08:11
@kixelated kixelated changed the title test(json): cover refresh through a two-relay cluster test(net): settle refresh as a soft trigger Oct 23, 2026
@coderabbitai

coderabbitai Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 2 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 923f448e-1250-4985-be69-741146b18751
📥 Commits

Reviewing files that changed from the base of the PR and between 69b0538 and e7633ee.

⛔ Files ignored due to path filters: 1
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing: 23
  • doc/concept/moq-lite.md
  • drafts/draft-lcurley-moq-lite.md
  • js/net/src/track.test.ts
  • js/net/src/track.ts
  • py/moq-rs/moq/json.py
  • quest/m1/README.md
  • quest/m1/api-audit/README.md
  • quest/m1/compress/README.md
  • quest/m1/ietf-extension/README.md
  • quest/m1/refresh/README.md
  • rs/moq-c/src/api.rs
  • rs/moq-c/src/publish.rs
  • rs/moq-ffi/src/json.rs
  • rs/moq-ffi/src/test.rs
  • rs/moq-json/src/snapshot/encoder.rs
  • rs/moq-json/src/snapshot/mod.rs
  • rs/moq-json/src/snapshot/producer.rs
  • rs/moq-json/src/window/producer.rs
  • rs/moq-net/Cargo.toml
  • rs/moq-net/src/model/track.rs
  • rs/moq-net/tests/integration/refresh.rs
  • rs/moq-video/src/encode/cuts.rs
  • rs/moq-video/src/encode/producer.rs
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-23T08:47:16.111511Z e7633ee New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4c6450a921

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread rs/moq-json/src/snapshot/mod.rs Resolved
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: db50567698

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread rs/moq-net/src/model/track.rs Resolved
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kixelated
kixelated added this pull request to the merge queue Oct 23, 2026
Merged via the queue into main with commit 3f72065 Oct 23, 2026
9 checks passed
@kixelated
kixelated deleted the quest/m1/refresh/README branch October 23, 2026 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant