Closed Muuut closed 1 day ago
same problem recurred on Qwen2.5-Coder-32B-instruct deployed by vllm, while Qwen2.5-32B-instruct support function calling as expected.
same problem recurred on Qwen2.5-Coder-32B-instruct deployed by vllm, while Qwen2.5-32B-instruct support function calling as expected.
I did not set the system content
in the message before. After setting, function calling works normally.
same problem recurred on Qwen2.5-Coder-32B-instruct deployed by vllm, while Qwen2.5-32B-instruct support function calling as expected.
I did not set the
system content
in the message before. After setting, function calling works normally.
Default qwen system prompt? I tried it, and still the problem that tool_calls is empty and content returns tool call string. Whether it is Qwen2.5-Coder-32B-instruct or Qwen2.5-Coder-7B-instruct, without any adjustments, only model switch to Qwen2.5-32B-instruct or Qwen2.5-7B-instruct can tool_calls be obtained correctly.
According to the documentation, I use VLLM to build a openai compatible server for qwen2.5-coder-7b-instruct.
That is my code
However, I got this: The finish_reason is "stop" instead of "tool_calls", and the tool_calls is empty. So I wonder whether qwen2.5-coder series support function calling?