Repository navigation
fix(tool_parser): treat qwen_xml tool-call arg values literally #1899
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 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
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.
In this test, the XML input uses
<function=write_file>, but thetoolslist is created usingtool_with_props, which defines a function named"f".Because of this mismatch,
helpers::param_types_for_function(tools, "write_file")returns an empty map, meaning the schema-typed path (coerce_value) does not find the"content"parameter's declared type ("string") and silently falls back to the schema-lesssafe_valpath. As a result, the schema-typedstringpath is not actually being tested here.Changing the function name in the XML template to
"f"ensures that the schema-typed path is correctly matched and exercised.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.
Good catch — you're right. With the tool named
fbut the XML declaring<function=write_file>,param_types_for_functionreturned an empty map, socoerce_valuegotdeclared_type=Noneand fell through tosafe_val. Both halves of the test were exercising the inference path;coerce_by_schema_type'sstringbranch was never hit.Fixed in 900d660 by matching the XML function name to the tool (
<function=f>), so the schema-typed path is now genuinely exercised. Thanks!