Skip to content

fix(render): retry transient network changes#2294

Open
miguel-heygen wants to merge 1 commit into
mainfrom
fix/retry-network-changed
Open

fix(render): retry transient network changes#2294
miguel-heygen wants to merge 1 commit into
mainfrom
fix/retry-network-changed

Conversation

@miguel-heygen

Copy link
Copy Markdown
Collaborator

What

Classify Chromium net::ERR_NETWORK_CHANGED navigation failures as transient capture errors.

Why

A Windows render failed mid-capture while navigating the local HyperFrames server with net::ERR_NETWORK_CHANGED; an immediate retry succeeded. The bounded browser retry classifier did not recognize this Chromium network-stack transition, so otherwise recoverable captures could fail on the first occurrence.

How

Add the error signature to the existing transient-browser classifier, which routes it through the already bounded fresh-session retry path. Add a regression case with the localhost URL form reported by Chromium.

Test plan

  • bunx vitest run src/services/frameCapture-transientErrors.test.ts (42 passed)
  • bun run typecheck
  • bunx oxfmt --check src/services/frameCapture.ts src/services/frameCapture-transientErrors.test.ts
  • bunx oxlint src/services/frameCapture.ts src/services/frameCapture-transientErrors.test.ts
  • Full engine suite: 942 passed; 2 unrelated VFR extraction tests failed because the host FFmpeg 4.2.2 does not support -fps_mode.

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