Limit parallelism of forced key ring refreshes #54627
Closed
Conversation
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
During the auto-refresh window, an `Unprotect` call with an unknown key ID is allowed to bypass the cache and perform a fresh read of the key ring (dotnet#11987). While, in principle, "force" means that it must happen every time, in practice, it doesn't make sense to block until an ongoing refresh is finished and then immediately perform another one. Instead, wait for the in-progress refresh to complete and return the same value (or throw, as appropriate). Preserving the precise exception from the thread that actually does the refresh didn't seem important, so I didn't bother (for now).
ghost
added
the
Member
Author
|
I'd like to discuss this change in isolation, but I actually have a different implementation in mind. |
Member
Author
|
The real change is #54675. |
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.
During the auto-refresh window, an
Unprotectcall with an unknown key ID is allowed to bypass the cache and perform a fresh read of the key ring (#11987). While, in principle, "force" means that it must happen every time, in practice, it doesn't make sense to block until an ongoing refresh is finished and then immediately perform another one. Instead, wait for the in-progress refresh to complete and return the same value (or throw, as appropriate).Preserving the precise exception from the thread that actually does the refresh didn't seem important, so I didn't bother (for now).