Retry schedule updates on conflict token mismatch - #1812
Open
ningmao-hlyz wants to merge 1 commit into
Open
Conversation
ningmao-hlyz
force-pushed
the
schedule-conflict-token-retry
branch
from
September 7, 2026 14:18
cc5b2a8 to
f238dd7
Compare
Author
|
Hi maintainers. The change passes the focused schedule conflict-token test and local Ruff, Ruff format, Pyright, BasedPyright, Mypy, pydocstyle, and diff checks. Could someone review the PR when convenient? Thanks! |
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.
What changed
Fixes #1367
Checks