Original tool calling issue persists

#4
by weisunding - opened

The original Qwen3.6 tool calling issue persists. (output tool calling as plain text, or not closing xml tag, ...)

c502ad92643946b6a43acf87fbf48fe6

Yea this seems to be a chat template level issue more than anything. It may help to use the froggeric template for Qwen3.6

Same with your earlier infinite thinking loop discussion (now deleted)

OK, I will try a chat template, thanks!

The infinite loop of thinking
image

Wow I've never encountered this issue at all.. Can i asked more details on how you're serving the model and what sampling params you're using?

I tried muliple chat templates, current used:
https://gist.github.com/jscott3201/e4b155885cc68c038d6ac8909a3bd9fe

My recipe

#!/bin/bash

NAME=qwen3.6-35b
PORT=3635

sudo docker stop $NAME > /dev/null 2>&1
sudo docker rm $NAME > /dev/null 2>&1

sleep 5

VLLM=vllm/vllm-openai:latest

sudo docker run \
    -d \
    --restart always \
    --runtime nvidia \
    --ipc=host \
    --gpus '"device=2,3"' \
    --name $NAME \
    -e HF_HUB_OFFLINE=1 \
    -e HF_ENDPOINT=https://hf-mirror.com \
    -e NCCL_P2P_DISABLE=1 \
    -e LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu \
    -v /data/model/huggingface:/root/.cache/huggingface \
    -v /data/model/modelscope:/root/.cache/modelscope \
    -v $(pwd)/chat:/chat \
    -p 127.0.0.1:$PORT:8000 \
    $VLLM \
    --model armand0e/Qwen3.6-35B-A3B-Fable-5-Distill \
    --served-model-name beast \
    --tensor-parallel-size 2 \
    --enable-auto-tool-choice \
    --reasoning-parser qwen3 \
    --tool-call-parser qwen3_coder \
    --chat-template /chat/chat_template.jinja \
    --default-chat-template-kwargs '{"enable_thinking": true}' \
    --speculative-config '{"method":"mtp","num_speculative_tokens":3}' \
    --gpu-memory-utilization 0.98 \
    --kv-cache-dtype fp8 \
    --max-model-len 204800 \
    --max-num-batched-tokens 8192 \
    --disable-custom-all-reduce \
    --enable-prefix-caching \
    --enable-chunked-prefill \
    --trust-remote-code
Owner

Interesting. Let me look into this more and get back to you. You said this is a known vllm issue?

Sign up or log in to comment