Skip to content

Conversation

@HaoK
Copy link
Member

@HaoK HaoK commented Jul 9, 2019

Fix for #3975

Note: Hard coded 5 minute window for now

@analogrelay analogrelay added the area-dataprotection Includes: DataProtection label Jul 9, 2019
@analogrelay analogrelay added this to the 3.0.0-preview8 milestone Jul 9, 2019
Copy link
Member

@GrabYourPitchforks GrabYourPitchforks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, per our email thread.

@HaoK HaoK merged commit d48ad7a into master Jul 9, 2019
@ghost ghost deleted the data-race branch July 9, 2019 20:42
amcasey added a commit to amcasey/aspnetcore that referenced this pull request Mar 19, 2024
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).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-dataprotection Includes: DataProtection

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants