fix: deduplicate concurrent signer credential refreshes - #842
Draft
Xuanwo wants to merge 2 commits into
Draft
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
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.
Concurrent
Signercalls can observe the same empty or stale credential cache and invoke the provider in parallel, causing issuance bursts at cold starts and refresh boundaries.This serializes credential refresh per shared cache with a runtime-agnostic async mutex. Callers waiting on a successful refresh reuse the cached credential. A failed or cancelled refresh is not cached, so the next waiting or later caller retries. Request signing runs after releasing the mutex, preserving concurrent signing, exact operation-validity checks, atomic request mutation, and the existing cache-sharing rules.
Fixes #837