Conversation
Report retry count on `Ok` results that underwent retries through a `RetryCount` response extension, so that users can include the retry count in error messages. We discovered in uv that we were not reporting retries for status code errors. This change does for `Ok` results what TrueLayer#159 did for `Err` results.
konstin
force-pushed
the
konsti/report-retry-counts
branch
from
62eed11 to
7a36fcc
Compare
konstin
added a commit
that referenced
this pull request
Aug 28, 2025
Report retry count on `Ok` results that underwent retries through a `RetryCount` response extension, so that users can include the retry count in error messages. We discovered in uv that we were not reporting retries for status code errors. This change does for `Ok` results what TrueLayer#159 did for `Err` results.
konstin
added a commit
that referenced
this pull request
Dec 18, 2025
Report retry count on `Ok` results that underwent retries through a `RetryCount` response extension, so that users can include the retry count in error messages. We discovered in uv that we were not reporting retries for status code errors. This change does for `Ok` results what TrueLayer#159 did for `Err` results.
konstin
added a commit
that referenced
this pull request
Feb 9, 2026
Report retry count on `Ok` results that underwent retries through a `RetryCount` response extension, so that users can include the retry count in error messages. We discovered in uv that we were not reporting retries for status code errors. This change does for `Ok` results what TrueLayer#159 did for `Err` results.
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.
Report retry count on
Okresults that underwent retries through aRetryCountresponse extension, so that users can include the retry count in error messages.We discovered in uv that we were not reporting retries for status code errors. This change does for
Okresults what TrueLayer#159 did forErrresults, enabling consistently showing retry messages in error traces (astral-sh/uv#13897).