Repository navigation
Tell a stale resume token from one that was never valid - #7
Merged
Merged
Conversation
liran
changed the title
liran
force-pushed
the
feat/tell-gone-steps-from-bad-tokens
branch
from
November 5, 2026 15:01
0f2878d to
a0669a3
Compare
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.
Resuming with an old token and resuming with garbage both come back as a resume token error, so a callback handler has to answer them the same way. The first is usually a late callback to ignore, and the second is a caller bug to report.
IsStaleResumeTokenErrorcovers only the first.IsResumeTokenErrorkeeps its meaning, so existing callers see no change.