-
-
Notifications
You must be signed in to change notification settings - Fork 22.3k
[Core] Distinguish reused from newly cached blocks in BlockStored #51699
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
fishercort
wants to merge
1
commit into
vllm-project:main
Choose a base branch
from
fishercort:blockstored-origin
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+67
−1
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: vllm-project/vllm
Length of output: 12362
🤖 get_repo_knowledge executed:
get_repo_knowledge vllm-project/vllm /tmp/coderabbit-repo-knowledge/vllm-project-vllm-8d5490deLength of output: 624
🌐 Web query:
msgspec Struct Decoder unknown fields ignored default forbid_unknown_fields documentation💡 Result:
In msgspec, unknown fields encountered when decoding into a Struct are ignored by default, which facilitates schema evolution and flexible decoding [1][2][3]. To prevent unknown fields from being ignored—for example, to catch typos in incoming data—you can configure the struct definition to forbid them [1][2]. By setting forbid_unknown_fields=True in the struct definition, any unknown field encountered during decoding will cause a msgspec.ValidationError to be raised [1][4][2]. Example usage: class Example(msgspec.Struct, forbid_unknown_fields=True): field_one: int field_two: bool = False If this class is used to decode data containing an unknown field (e.g., {"field_one": 1, "field_twoo": true}), msgspec will raise a ValidationError [1][2]. The forbid_unknown_fields parameter is a boolean that defaults to False [4]. It is available in the Struct class definition and can be inspected in the struct's metadata [4]. While there have been community discussions regarding broader configuration options for decoders (e.g., issue
#796), the primary mechanism for controlling this behavior remains the configuration of the individual Struct definition [5].Citations:
Keep the copied subscriber schema in sync.
examples/features/kv_events/kv_events_subscriber.pydecodesBlockStoredwith a schema that omitsorigin. Becausemsgspec.Structignores unknown fields by default, the decoder discardsorigin, so the example cannot displayNEWorREUSED. Addorigin: str | None = Noneor import the canonical schema, and add a decoder smoke test.🤖 Prompt for AI Agents
Source: MCP tools