Repository navigation
Conversation
karya0
temporarily deployed
to
external_collaborator
October 19, 2026 21:04 — with
GitHub Actions
Inactive
karya0
temporarily deployed
to
external_collaborator
October 19, 2026 21:04 — with
GitHub Actions
Inactive
Contributor
karya0
force-pushed
the
kvcr-guard-sglang
branch
from
October 20, 2026 21:13
a8ef01c to
3dfb227
Compare
karya0
temporarily deployed
to
external_collaborator
October 20, 2026 21:13 — with
GitHub Actions
Inactive
Contributor
|
/ok to test 3dfb227 |
karya0
force-pushed
the
kvcr-guard-sglang
branch
from
October 20, 2026 21:32
3dfb227 to
ec5db30
Compare
karya0
temporarily deployed
to
external_collaborator
October 20, 2026 21:32 — with
GitHub Actions
Inactive
Contributor
|
/ok to test ec5db30 |
karya0
force-pushed
the
kvcr-guard-sglang
branch
from
October 20, 2026 22:26
ec5db30 to
bd4799b
Compare
karya0
temporarily deployed
to
external_collaborator
October 20, 2026 22:26 — with
GitHub Actions
Inactive
Contributor
|
/ok to test bd4799b |
karya0
force-pushed
the
kvcr-guard-sglang
branch
from
October 20, 2026 22:29
bd4799b to
a310f33
Compare
karya0
temporarily deployed
to
external_collaborator
October 20, 2026 22:29 — with
GitHub Actions
Inactive
Contributor
|
/ok to test a310f33 |
Contributor
✅ Dynamo PR CI passed — run 40448994647 (attempt 1) on
|
This was referenced Oct 21, 2026
3 of 4 tasks
Opt in with --kvcr-state-agent-owner on an aggregated direct-linker worker: register one state-agent attachment after engine init, advertise kv_event_source_mode=state_agent_v2, and skip the legacy KV event publisher. Native registration rolls itself back when its waiter is dropped, so startup cancellation needs no Python-side cleanup. Signed-off-by: Kapil Arya <kapila@nvidia.com>
karya0
force-pushed
the
kvcr-guard-sglang
branch
from
October 27, 2026 04:18
a310f33 to
a7f1bc5
Compare
karya0
temporarily deployed
to
external_collaborator
October 27, 2026 04:18 — with
GitHub Actions
Inactive
Contributor
|
/ok to test a7f1bc5 |
This branch was previously 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.
Stacked on #16117 (base branch
codex/glm53-kvcr-hicache). The first commit cherry-picks the lychee link fix from #16573 that the base branch has not picked up yet; the second commit is this PR.An aggregated SGLang worker running the direct KVCR linker can opt in with
--kvcr-state-agent-owner <CacheOwnerId>. The worker then registers one attachment with the external KV state agent after engine init and withdraws it on shutdown. The attachment carries the raw ZMQ event endpoint, the KV block size, and arouter_hint_sourcenaming the linker's source-control endpoint, so the state agent indexes the cache under a stable owner and the router can keep hinting at it after the worker is gone and the KVCR Guard holds the pool.With the flag set, the worker registers
kv_event_source_mode = "state_agent_v2"and skips the legacy KV event publisher;use_kv_eventsstays advertised. Without the flag nothing changes.Validation rejects anything other than an aggregated linker worker with KV events, a ZMQ TCP event publisher on an empty topic, and remote linker hints enabled.
kvcr_hint_sourcesis split out ofpublish_kvcr_hint_capabilitiesso the attachment and registration resolve the same endpoint.Cancelling startup needs no Python-side cleanup: the native owner withdraws its own registrations when its waiter is dropped, as the vLLM attachment relies on already.
🤖 Generated with Claude Code