Skip to content

chore(quest): record fixed-delay deployment verification blocker - #6429

Closed
kixelated wants to merge 4 commits into
mainfrom
quest/m0/release-fixed-delay
Closed

kixelated wants to merge 4 commits into
mainfrom
quest/m0/release-fixed-delay

Conversation

@kixelated

@kixelated kixelated commented Oct 23, 2026 •

Copy link
Copy Markdown
Collaborator

Problem

The release verification quest remains open until moq.dev deploys the fixed-delay behavior and live numeric selections are verified under changing catalog estimates.

Approach

Update the quest with proven publication of the 6217 backport, retaining the precise site dependency/deployment condition.

const configured = effect.get(this.in.delay);
if (typeof configured === "number") {
    this.#out.delay.set(configured);
    return;
}

Earlier live UI evidence remains limited to displayed diagnostics:

Active preset Displayed jitter buffer Displayed total buffer
100 ms 100 ms 475 ms
250 ms 250 ms 625 ms
100 ms, repeated 100 ms 475 ms

These were not glass-to-glass measurements. The extra 375 ms was not attributed to particular catalog fields, and estimate growth was not controlled. Observed Astro asset names exposed no deployed revision. No new browser session was opened for this evidence update.

Impact

  • Public API and wire: unchanged. Only quest evidence changed; the consumer remains the moq.dev viewer.
  • No player source, dependency, version, or deployment changes.

Validation

  • Fresh origin/main merged cleanly into the existing branch; no conflict remained.
  • Nix just ci passed: quest, Markdown, shell, TOML, Nix, justfile, and GitHub checks. Rust/build tests were not selected for the quest-only delta.
  • Nix quest check --base origin/main passed: 588 documents.
  • git diff --check passed.
  • Original evidence retained; new emitted-branch/source-map proof and CI log preserved in the worktree's ignored .scratch/validation/.

Alternatives

Use the existing published fix and establish its site deployment. Another player implementation or backport would duplicate completed work.

Decisions needed

Site dependency/deployment ownership must deploy a package containing the fix. Then establish deployed build provenance and verify fixed 100/250 ms resolved targets while nonzero catalog delay/jitter changes. Recommend keeping this draft and the quest open until both pass. This checkpoint does not choose a version or perform a deployment.

Follow-ups

All remaining work stays in the same quest. No new quest, site PR, or deployment was created.

(Written by GPT-6)

kixelated and others added 2 commits October 22, 2026 17:59
@kixelated kixelated changed the title A fixed latency on release ignores the catalog jitter and delay chore(quest): record fixed-delay deployment verification blocker Oct 23, 2026
@kixelated

Copy link
Copy Markdown
Collaborator Author

Closing as a duplicate of moq-dev/moq#6333, which completes release-fixed-delay: @moq/watch 0.6.5 (with the fix) is on npm, so what's left is bumping moq.dev to it and checking the deployed bundle.

(Written by Claude Opus 5.5)

@kixelated kixelated closed this Oct 23, 2026
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