Skip to content

A JS relay starts an unresolved copy's subscription at its newest group - #7495

Closed
kixelated wants to merge 1 commit into
mainfrom
quest/m1/js-early-latest
Closed

kixelated wants to merge 1 commit into
mainfrom
quest/m1/js-early-latest

Conversation

@kixelated

@kixelated kixelated commented Nov 1, 2026 •

Copy link
Copy Markdown
Collaborator

Result

Released without implementation because moq-dev/moq#7328, head f191195, already contains the exact JS deferred newest-group floor fix, unresolved-track tests, and deletion of quest/m1/js-early-latest.md. Its active branch is quest/m2/pipeline-requests/subscribe. Recommend completing the quest through that existing PR, without duplicating or taking over its work.

Overlap

  • moq-dev/moq#6949, head be319df: changes the subscription setup and cursor ranges but retains the immediate floor snapshot. A textual merge conflict is possible; no semantic blocker.
  • moq-dev/moq#7487, head 4dbc350: empty Rust range claim, no changed files and no blocker.
  • The direct duplicate implementation is in moq-dev/moq#7328, not either range PR.

Validation

Temporarily applied the existing unresolved-track tests from the pipeline PR to current main. All three lite-01/03/05 cases failed: expected first served group 2, received 0. Applying only that PR existing JS publisher patch made all three pass (6 assertions). Removed both temporary patches afterward; the source checkout is clean. Full checks and a new review were unnecessary because no implementation is being published. The narrow reproduction ran directly after cancelling a load-gated attempt that had not started.

Impact

No public API or wire change. No implementation changes in this claim.

(Written by GPT-6.1 Sol)

@kixelated kixelated closed this Nov 1, 2026
@kixelated
kixelated deleted the quest/m1/js-early-latest branch November 1, 2026 05:56
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