Repository navigation
Run an elected caller's own factory instead of sharing a run in flight - #49
Merged
Merged
Conversation
…rom before the invalidation
aisk
force-pushed
the
factory-reelect-own-run
branch
from
October 6, 2026 17:58
8ece148 to
1e2ad46
Compare
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
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.
A caller that won a fresh lease while another factory run for the same key was in flight in the same client used to share that run's value and write it back through its own lease. If the key had been deleted in between, this put a value computed before the delete back into the cache. An elected caller now always runs its own factory, and only callers the server did not elect share a run in flight.