-
-
Notifications
You must be signed in to change notification settings - Fork 15.5k
Fix: Handle $ref in json-schema in qwen3_coder tool parser #37652
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
Closed
schoennenbeck
wants to merge
2
commits into
vllm-project:main
from
schoennenbeck:fix/qwen3-tool-parser-jsonrefs
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
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.
This change correctly identifies parameters defined with
$ref, but making the broad assumption that they are always ofobjecttype could lead to incorrect behavior.A
$refcan point to a definition of any type, including primitives likestringorinteger. If a$refpoints to a string type, but the model returns a value that looks like a dictionary (e.g.,"{'key': 'value'}"), the current logic would incorrectly parse it as a dictionary viaast.literal_evalin the fallback path, instead of treating it as a string. This would result in a type mismatch and potential runtime errors in the tool-using code.A safer approach would be to handle
$refparameters separately, perhaps by attempting to parse them withjson.loadsand falling back to treating them as a raw string if parsing fails, without attemptingast.literal_eval. This would correctly handle object-like values while not misinterpreting string literals that happen to look like Python literals.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.
Switched to more restrictive parsing, avoiding the
ast.literal_evalfor refs.