fix(vllm): validate persistent container configuration - #327
Draft
nvddr wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Devdeep Ray <devdeepr@Nvidia.com>
nvddr
force-pushed
the
agent/vllm-config-fingerprint
branch
from
July 31, 2026 20:54
e34df37 to
d3c198e
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
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.
Summary
Why
A persistent container could be restarted with model arguments, GPU assignment, or memory limits from an older profile even after the active YAML changed.
Validation
uv run --project tests pytest -q tests/test_vllm_docker.pyruff checkon changed Python files