OpenAI tool-call compatibility issue in flare that kills agentic loops

Abierto
  • ¿Algo no está bien?
#32 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
api, backend

Línea de trabajo

Start by locating the completion stream code that raises “model called unregistered tool” for newly generated calls; the issue names no source file or test. Compare that path with the accepted history case, then trace how tool calls and recoverable errors reach clients. Done means an unregistered generated call can be handled by the client and the turn can continue; add coverage for that recovery path.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:api bug triage:verify-for-closure

What happens: when the model emits a tool_call whose function name isn't in the request's tools schema (e.g. run_commands instead of run_command), flare aborts the completion with model called unregistered tool …. Clients are designed to receive that call, return a "no such tool" result, and let the model correct itself in the same turn — the Open WebUI maintainer confirmed its loop does exactly that. Flare terminates the stream first, so the recovery never runs and the whole turn/agent loop dies. Seen live in OWUI: the loop just stops on that error.

Evidence:

The error is flare's own: model called unregistered tool … sits in the engine binary at offsets ~1127283/1127296 (/usr/local/bin/flare).
Control: the same unregistered name placed in history (assistant tool_calls + tool-role error result) is accepted — HTTP 200, model recovers and calls run_command correctly. So the rejection fires only on newly generated calls.
Black-box forcing didn't work (the model refuses to emit invalid names when instructed; 30 samples at temp 1.5, all run_command), but the check is deterministic once a bad name is generated — a canned invalid generation feeds straight into it.
vLLM/SGLang pass emitted tool calls through verbatim; name routing is the client's contract. That's why this never appeared before.
Suggested fix: don't hard-fail on an emitted name that isn't in the schema — either pass the call through as-is (client dispatches or errors), or surface it as a recoverable error event/tool-call so the client's own recovery can run.

Lenguaje dominante
Rust
Estrellas
800
Forks
106
Merge medio
1 d 3 h
PR fusionados (30 d)
100

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de NVIDIA/hyperflare-inference

Todos los issues de NVIDIA/hyperflare-inference

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.