Dispatcher.ReplaceImplementation bugfix - #21735
Merged
MrJul merged 1 commit intoJul 9, 2026
Merged
Conversation
âĶ were submitted before ReplaceImplementation
kekekeks
force-pushed
the
fix/dispatcher-loses-early-state-in-replace-implementation
branch
from
July 9, 2026 05:33
3a91060 to
022ceb3
Compare
|
You can test this PR using the following package version. |
MrJul
added
the
backport-candidate-12.1.x
MrJul
added this pull request to the merge queue
Jul 9, 2026
MrJul
removed this pull request from the merge queue due to a manual request
Jul 9, 2026
MrJul
deleted the
fix/dispatcher-loses-early-state-in-replace-implementation
branch
July 9, 2026 15:53
MrJul
pushed a commit
that referenced
this pull request
Jul 29, 2026
âĶ were submitted before ReplaceImplementation (#21735)
MrJul
added
backported-12.1.x
and removed
backport-candidate-12.1.x
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
3 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've missed a call to RequestBackgroundProcessing to a new implementation previously, this caused dispatcher to think that it has already requested processing.