Repository navigation
Respect RetryAfterer through error wrapping - #6
Merged
Merged
Conversation
nodivbyzero
approved these changes
Oct 4, 2026
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
2 participants
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.
I run Live Tennis API.
Wrapping a RetryAfterer with fmt.Errorf currently hides its delay and invokes the fallback schedule. Use errors.As to find the requested delay through wrappers and errors.Join.
MaxDelay still caps the wait, and RetryAfterer still takes precedence over WithDelayFunc. An outer RetryAfterer keeps precedence over a nested one.
Eight new cases cover those behaviors and the fallback for errors without RetryAfterer. Five cases fail on unchanged upstream.
On Go 1.27.0,
go test ./... -v -race -coverpasses with 95.9% coverage.go build ./...,go vet ./...and formatting checks also pass.