Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Bug]: OpenAI-compatible tool calls are returned as plain text when routed through PAIR

Aperta
  • Qualcosa non va?
#94 7 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 5 giorni

@kjlubick ci sta già lavorando.

Dal 1/10/2026.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, ollama
Ambito
api, backend

Direzione di ricerca

Inizia dal punto di ingresso /v1/chat/completions del proxy Ollama e confronta il modo in cui vengono gestite le richieste e le risposte quando sono presenti definizioni di strumenti. Riproduci il problema con la richiesta curl documentata verso PAIR e direttamente verso Ollama, quindi verifica che PAIR conservi message.tool_calls e finish_reason: tool_calls invece di restituire la chiamata come testo.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
PAIR version or commit

0.1.1-463

Affected component

Ollama proxy

Environment

OS: Ubuntu 26.04.1 LTS on model host; Linux on NVIDIA DGX Spark PAIR client
Architecture: x86_64 model host; arm64 PAIR client
GPU and driver: AMD Radeon 8060S / Ryzen AI Max+ 395 on model host; NVIDIA GB10 on PAIR client
Engine and version: Ollama 0.33.2
Model: qwen3.6:27b
Cluster size: 4 nodes

Steps to reproduce

  1. Configure a PAIR cluster with an Ollama node serving qwen3.6:27b.

  2. Send an OpenAI-compatible POST request to:
    /v1/chat/completions

    The request contains multiple OpenAI function/tool definitions and asks the model to work on a task for which it should call the kanban_show function.

  3. Send the request through the PAIR Ollama proxy.

  4. Send the exact same JSON request body directly to the Ollama server hosting qwen3.6:27b, bypassing PAIR.

  5. Compare finish_reason, message.content, and message.tool_calls in the two responses.

Repeated control test:

  • Direct to Ollama: 3/3 requests returned a native tool_calls object.
  • Through PAIR: 3/3 requests returned finish_reason: stop with no tool_calls object. The intended function call instead appeared as ordinary assistant content.

The behavior is reproducible with curl and does not require an agent framework.

Expected behavior

When an OpenAI-compatible chat completion request containing tool definitions is routed through PAIR, native tool-calling behavior should be preserved.

For this request, the response should contain message.tool_calls with a call to kanban_show, and finish_reason should be tool_calls, matching the response obtained when the identical request is sent directly to the Ollama server.

Actual behavior

When the identical request is sent through the PAIR Ollama proxy, the native OpenAI-compatible tool call is not returned.

In repeated testing, PAIR returned:

  • finish_reason: stop
  • message.tool_calls: null / absent
  • The intended kanban_show call embedded in message.content as ordinary text.

Three consecutive PAIR requests produced textual representations such as:

  1. Python-like syntax:
    kanban_show(task_id="t_65ba4229")

  2. Bracket syntax:
    [kanban_show][0]

  3. XML-like syntax:
    <invoke>kanban_show(task_id="t_65ba4229")</invoke>

By contrast, three consecutive requests using the identical JSON request body sent directly to Ollama returned native OpenAI-compatible tool calls:

finish_reason: tool_calls

with message.tool_calls containing a function call to kanban_show.

The same JSON payload succeeds when sent directly to the Ollama server on the model host, so the failure is introduced only when the request is routed through PAIR.

This also prevents OpenAI-compatible agent/tool frameworks from recognizing and executing the requested function when the request is routed through PAIR.

Sanitized logs or screenshots
Confirmations
  • I searched existing issues for duplicates.
  • This is not a security vulnerability.
  • I agree to follow the Code of Conduct.
Lingua principale
Go
Stelle
1.6k
Fork
266
Merge medio
3g 15h
PR unite (30g)
23

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di NVIDIA/Personal-AI-Router

Tutte le issue di NVIDIA/Personal-AI-Router

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.