Skip to content

fix(tui): retry migration status transport errors - #42188

Closed
kitlangton wants to merge 1 commit into
v2from
retry-migration-status
Closed

kitlangton wants to merge 1 commit into
v2from
retry-migration-status

Conversation

@kitlangton

Copy link
Copy Markdown
Contributor

What

Keep the migration status overlay polling through temporary server transport loss.

Before / After

Before

A transient disconnect while the background service restarted ended migration polling and displayed a migration failure toast.

After

Transport errors retry after one second. Actual API or migration errors still surface, and unmount aborts polling without a stale toast.

How

  • Retries only ClientError transport failures in packages/tui/src/component/migration-overlay.tsx.
  • Checks the abort signal before and after retry delays.
  • Suppresses cleanup-triggered error presentation.

Scope

This PR does not change service version policy, replacement, stop behavior, discovery validation, service election, or TUI layout.

Testing

  • cd packages/tui && bun run test test/component (10 passed)
  • cd packages/tui && bun typecheck
  • Repository pre-push typecheck: 34 packages passed

@kitlangton

Copy link
Copy Markdown
Contributor Author

Closing because we do not currently have a captured migration failure or regression test demonstrating this retry path. The change is plausible, but we should reproduce the transport failure and verify retry semantics before changing polling behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant