Repository navigation
Migration readiness retries transient GitHub API errors - #4576
Merged
Merged
Conversation
…etwork cause The runner on slow-fetch heads (48 commits of merged history) failed closed with a TypeError at the GitHub API stage. Reads now retry up to three times with a 30 s timeout; rule refusals are never retried. The failure line includes the cause code. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012BMmZWrkFxXJddyVkAXF4c
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The readiness runner fails closed on #4556, #4560 and #4568 with
Migration readiness error TypeError ... stage=github-api(read from the #4574 diagnostics). A TypeError from fetch is a network or stalled-body failure, not one of our rules, and the failing heads spend 60 to 85 s on a slowfetch --filter=blob:nonefirst.GitHub reads now use a 30 s timeout and retry up to three times with a short backoff. Our own rule refusals (
safeerrors) are never retried. The failure line also reports the underlying cause code. No readiness rule changes.Checked:
vitest runon publish-migration-readiness.test.ts and migration-pr-readiness.test.ts, 114 pass.Generated by Claude Code