Repository navigation
engine: honour Retry-After when retrying a rate-limited module fetch - #260
Merged
Merged
Conversation
A module answered 429 was retried after a fixed 150ms and 300ms, inside the window the origin asked us to wait, and could be dropped, breaking the page. Reuse the image path's Retry-After parsing so the wait matches the origin's request. Stash-verified: the old code drops the module at 0.46s; the fix fetches it after the 1s the origin asked for. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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.
A module answered 429 was retried after a fixed 150ms and 300ms, inside the window the origin asked us to wait, and could be dropped, breaking the page. Module retries now wait for Retry-After when present, reusing the image path's parsing.
🤖 Generated with Claude Code