Backport vLLM structured-output reasoning boundary fix (#44297 + #44993) - #19
Draft
danielmccannsayles wants to merge 1 commit into
Draft
Backport vLLM structured-output reasoning boundary fix (#44297 + #44993)#19danielmccannsayles wants to merge 1 commit into
danielmccannsayles wants to merge 1 commit into
Conversation
…oundary Fixes GLM-5.2 tool-call 500s and malformed JSON under MTP spec decode + reasoning. #44297 (merged, post-v0.24.0) constrains the reasoning-end bitmask and trims grammar advance; #44993 (open, approved, stacked on #44297) advances the grammar across the boundary for all constraint types. Both verified to apply cleanly to v0.24.0 with patch -p1 --fuzz=0.
danielmccannsayles
changed the title
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.
Fixes the GLM-5.2 tool-call 500s and malformed JSON under MTP spec decode + reasoning. Neither patch is in v0.24.0 yet — #44297 merged to main after the cut, #44993 is still open. Both required (44993 stacks on 44297).