Skip to content

fix: support vLLM 0.31 inference history hooks - #1136

Merged
bradhilton merged 3 commits into
mainfrom
fix/jarvis-vllm031-responses
Oct 22, 2026
Merged

bradhilton merged 3 commits into
mainfrom
fix/jarvis-vllm031-responses

Conversation

@bradhilton

@bradhilton bradhilton commented Oct 21, 2026 •

Copy link
Copy Markdown
Collaborator

Agent: Jarvis

Qwen3.6 B300 /v1/responses returns HTTP 500 because vLLM 0.31 removed _make_request. Feature-detect the native _render_resolved_response_inputs result while keeping the vLLM 0.24 path unchanged; preserve completed responses when optional re-rendering returns a native error. Patch the relocated construct_input_messages alias so previous-response reasoning/tool history survives.

The hook audit also found that vLLM 0.31 passes DeepSeek V3.2 a cached full-chat last_user_idx, bypassing ART's historical-prefix truncation. Discard that cached index only for preserved prefixes so the native renderer recomputes it.

Validation: 293 history, append-only, token-prefix, chat-template and SGLang tests pass; changed-file type checking and Ruff pass. Tests cover both Responses shapes, streaming, previous-response lookup, native render errors and tool history. Downloaded/audited PyPI vLLM 0.24.0/0.31.0 sources; direct native DeepSeek encoding reproduces the regression before this fix and passes on both versions afterward. No GPU or production inference smoke was run.

Caladan adoption requires its five source/runtime pin files to be updated after this PR merges, followed by a rebuilt B300 runtime and Responses canary. This PR does not deploy anything.

🤖 Generated with Claude Code

@bradhilton bradhilton changed the title fix: support vLLM 0.31 Responses history rendering fix: support vLLM 0.31 inference history hooks Oct 21, 2026
@bradhilton
bradhilton merged commit 922cbf5 into main Oct 22, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant