Repository navigation
fix(tool_parser): preserve Qwen XML streamed arguments #2490
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
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.
🟡 Nit: Truncating the scan at the first
</tool_call>silently changes behavior for parameter values that contain the literal</tool_call>, and nothing pins the new behavior.For
<tool_call><function=process><parameter=snippet>use </tool_call> tag</parameter></function></tool_call>:snippet = "use </tool_call> tag", and the brace counter appended}— the client received the complete, valid{"snippet": "use </tool_call> tag"}(plus the leftovertag</parameter>…leaking as normal text).parameter_endlands mid-value, the slice is<parameter=snippet>usewith no</parameter>, so the parameter never matches and the call closes as{}— the argument is dropped entirely.This is arguably the right call:
parse_complete_inner's non-greedy(?s)<tool_call>\s*(.*?)\s*</tool_call>extractor already truncates at the same point and yields{}, so streaming and non-streaming now agree, and vLLM/SGLang split the same way. But the PR description lists this under "existing delimiter ambiguity … remain outside this change", when the change actually flips it from "correct args" to "empty args". Worth a short regression test intool_parser_qwen_xml.rsassertingjson!({})for that fixture, so the alignment withparse_completeis intentional and stays that way.