revert: remove fast-path message destination cache#10243
Merged
ReubenBond merged 1 commit intoJun 30, 2026
Conversation
Reverts the message destination receiver cache changes from dotnet#10064, the dependent dotnet#10080 follow-up, and the dotnet#10235 stale-cache fix now present on main. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Problem
The fast-path message destination cache introduced in #10064 caused the 10.2 regression tracked by #10238. The 10.2.1 release branch reverted that cache via d3c2af3.
Solution
Revert the message destination receiver cache changes on main:
Microsoft Reviewers: Open in CodeFlow