ERROR [qwen3coder_tool_parser.py:344] Error in extracting tool call from response. ERROR [qwen3coder_tool_parser.py:344] Traceback (most recent call last): ERROR [qwen3coder_tool_parser.py:344] File ".../qwen3coder_tool_parser.py", line 317, in extract_tool_calls ERROR [qwen3coder_tool_parser.py:344] self._parse_xml_function_call(function_call_str, request.tools) ERROR [qwen3coder_tool_parser.py:344] File ".../qwen3coder_tool_parser.py", line 259, in _parse_xml_function_call ERROR [qwen3coder_tool_parser.py:344] idx = match_text.index(">") ERROR [qwen3coder_tool_parser.py:344] ^^^^^^^^^^^^^^^^^^^^^ ERROR [qwen3coder_tool_parser.py:344] ValueError: substring not found

TL;DR

Replace str.index(">") with str.find(">") in Qwen3CoderToolParser._parse_xml_function_call to safely handle malformed parameters.

Guidance

• Identify the line of code using str.index(">") in Qwen3CoderToolParser._parse_xml_function_call and replace it with str.find(">").
• Add a conditional check to skip parsing when str.find(">") returns -1, indicating a malformed parameter.
• Verify the fix by testing with a model output containing a truncated parameter, ensuring that well-formed parameters are still parsed.
• Review the existing safe pattern used for the function name path to ensure consistency in handling malformed inputs.

Example

idx = match_text.find(">")
if idx == -1:
    # Skip parsing and log a warning for the malformed parameter
    print("Warning: Malformed parameter encountered. Skipping...")
    continue

Notes

This fix assumes that the str.find(">") method is sufficient for handling malformed parameters. Additional error handling or input validation may be necessary depending on the specific requirements of the Qwen3CoderToolParser.

Recommendation

Apply the workaround by replacing str.index(">") with str.find(">") and adding a conditional check to skip malformed parameters, as this will allow the parser to handle truncated parameters without discarding well-formed data.