Skip to content

Integration viewer: follow-ups from the #124 review (P2) #145

Description

@SamGu-NRX

Follow-ups from the Codex review of #124 at d966a09, left open on purpose so the PR could finish for the demo. Each is a P2 in tools/integration-viewer, and each thread on #124 has the detail.

  • The synthetic outage misses long polls in flight. #124 thread. An events long poll that starts just before the synthetic API's 11 s dropout keeps waiting and can answer during the outage. The API should recheck the outage after each wait and drop the pending request. This affects only the synthetic demo of reconnection.
  • A failing events poll blocks the result read. #124 thread. When the status read succeeds with a terminal status but the events read fails, the loop's continue skips the result and preview reads. If only the events endpoint stays down, no outcome ever shows. The result read should run after a successful status read, whatever happens to the events read.
  • A pending result can briefly show "Reading it…". This one is cosmetic, found while testing: during a refresh the model caption can flash the reading text. It needs no review cycle of its own.

These tests exist in tools/integration-viewer/test/, and node --test "test/*.test.js" runs them. CI does not run them yet.

Activity

  1. SamGu-NRX commented on Sep 27, 2026

    @SamGu-NRX
    OwnerAuthor

    The Codex review of 9c0680b, the final head of #124, raised no P1 and five P2s. They are recorded here instead of fixed, per the bounded-repair decision.

    • Status fields from a retired run. thread. A delayed status for a retired run no longer switches the run, but applyStatus still copies that response's status and filesRegistered before checking. It should reject the whole response when its runId is retired. This is the first one to take: it can mark the current run's running stages as unended and change when its result is read.
    • Retry-After on preview retries. thread. Preview retries use a fixed 5 s, and relayPreview does not pass Retry-After through from its own result or storage fetch.
    • A preview removed between reads. thread. A 404 preview_not_available from the relay should trigger a result re-read, as a 409 does, instead of retrying the preview.
    • The final count after a batch with no animation. thread. When an older landing timer is still pending and a newer batch cannot animate, the newest total is written only on the next state change. The last timer to fire should write the current counts.
    • The viewer suite in CI. thread. make check and CI do not run tools/integration-viewer. Adding them touches the root Makefile and a workflow, which needs the owners' agreement.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions