Repository navigation
perf: restore asynchronous route publication for Owner writes - #64
Merged
Merged
Conversation
ActivePeter
had a problem deploying
to
OPENAI_API_KEY
October 27, 2026 17:21 — with
GitHub Actions
Failure
ActivePeter
had a problem deploying
to
OPENAI_API_KEY
October 27, 2026 18:47 — with
GitHub Actions
Failure
This branch had an error being deployed
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.
External Owner-local PUTs currently wait for Master route publication after the values are already locally readable. Return success after local commit and handoff to the existing Owner publication task, removing Master publication latency from the PUT completion path used by SGLang KV cache writes.
The Owner task continues to hold pending contexts and per-key fences through publication, retry, and terminal cleanup. Successful completion confirms local commit; global route visibility remains eventual, and cross-owner readers must use actual GET results. Background publication failures are logged and handled by the existing publication lifecycle.
Update the regression coverage for both transfer-end and commit entrypoints to check acknowledgement while publication is paused, retained fences and readable holders after the caller leaves, eventual publication, and safe cleanup of independently rejected items. Tests that require a global route now wait for publication explicitly.
Validation: