-
Notifications
You must be signed in to change notification settings - Fork 295
Retry gateway errors on idempotent GraphQL requests #8450
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
craigmichaelmartin
wants to merge
1
commit into
main
Choose a base branch
from
retry-gateway-errors
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| '@shopify/cli-kit': patch | ||
| --- | ||
|
|
||
| Retry gateway errors (502/503/504) on GraphQL queries instead of failing immediately |
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,29 @@ | ||
| /** | ||
| * Pure helpers for classifying HTTP statuses that come from the gateway in front of an API rather | ||
| * than from the API itself. | ||
| * | ||
| * This module is intentionally dependency-free so that both the request layer (`../api.ts`) and the | ||
| * crash-report suppression logic in `../../public/node/error.ts` can share it. `error.ts` cannot | ||
| * import `../api.ts` directly — that would pull `graphql-request` into the module graph of every | ||
| * command, and `api.ts → headers.ts → error.ts` is already a cycle — so the shared status logic | ||
| * lives here, where it imports nothing from cli-kit. | ||
| */ | ||
|
|
||
| /** | ||
| * Statuses commonly emitted by a proxy or load balancer that could not produce a usable response | ||
| * from an upstream service: 502 Bad Gateway, 503 Service Unavailable, 504 Gateway Timeout. | ||
| * | ||
| * 500 is deliberately excluded: it means the API itself answered and failed, so it keeps its | ||
| * existing non-retryable, reportable behaviour. | ||
| */ | ||
| const GATEWAY_ERROR_STATUSES = new Set([502, 503, 504]) | ||
|
|
||
| /** | ||
| * Whether an HTTP status indicates a gateway-level failure in front of the API. | ||
| * | ||
| * @param status - The HTTP status of the response, if known. | ||
| * @returns True when the status is 502, 503 or 504. | ||
| */ | ||
| export function isGatewayErrorStatus(status: number | undefined): boolean { | ||
| return status !== undefined && GATEWAY_ERROR_STATUSES.has(status) | ||
| } |
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Retry-After: 60is actually waiting 60 ms, and a date 60 seconds ahead waits 1 second. This can exhaust retries before recovery. We should convert seconds to milliseconds and support HTTP dates.