Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Command code GOAT used via API: MiMo V2.6 Pro stream consistently fails at ~785s with

Abierto
  • ¿Algo no está bien?
#940 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Área
api, backend, observability

Línea de trabajo

Start by inspecting CommandCode trace b416c51c0eb32fde7cd20646bfd99625 and the Provider API route for the xiaomi/mimo-v2.6-pro request. Compare the 785.097-second termination with the gateway_stream_timeout and the COMPLETED record in CommandCode Studio. Done means identifying the timeout source and determining whether the failure status and upstream handling need correction.

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

Descripción

Summary

I am using the CommandCode GOAT API through OpenCode in Zed. Long-running autonomous agent sessions occasionally fail when an individual xiaomi/mimo-v2.6-pro inference runs for approximately 13 minutes.

The latest failure produced:

Internal error: {"code":"gateway_stream_timeout","message":"Stream exceeded maximum duration before function timeout","origin":"gateway"}: {
  "service": "session",
  "errorName": "UnknownError"
}

The corresponding request in CommandCode Studio is:

Model: xiaomi/mimo-v2.6-pro
Duration: 785.097s
Input tokens: 0
Output tokens: 0
Cost: $0.0000
Status: COMPLETED
Trace ID: b416c51c0eb32fde7cd20646bfd99625

Dashboard timestamp: Sep 27, 2:54:10 PM (as displayed in Studio).

Expected Behavior

Continue streaming without ~13 minutes timeouts.

Actual Behavior

"Stream exceeded maximum duration before function timeout"

Steps to reproduce the issue
  1. Configure OpenCode in Zed to use the CommandCode API (Provider API?).
  2. Select xiaomi/mimo-v2.6-pro.
  3. Run a long autonomous coding-agent session. ZDR is not enabled.
  4. When an individual MiMo inference runs for approximately 13 minutes, the request terminates with:
Internal error: {"code":"gateway_stream_timeout","message":"Stream exceeded maximum duration before function timeout","origin":"gateway"}: {
  "service": "session",
  "errorName": "UnknownError"
}
  1. In CommandCode Studio, the corresponding request is recorded as:
Model: xiaomi/mimo-v2.6-pro
Duration: 785.097s
Input tokens: 0
Output tokens: 0
Cost: $0.0000
Status: COMPLETED
Trace ID: b416c51c0eb32fde7cd20646bfd99625

Other MiMo requests in the same session completed successfully, including requests lasting approximately 545s, 399s, and 317s.

The overall agent session was about 32m25s long. The failure appears tied to the duration of one individual streaming inference, not the total session duration.

Command Code Version

N/A

Operating System

Linux

Terminal/IDE

Zed + OpenCode via ACP

Shell

N/A — issue occurs through Zed/OpenCode

Session file (optional)

Not attached. The relevant CommandCode trace is:

b416c51c0eb32fde7cd20646bfd99625

Fix prompt (optional)

Please inspect trace b416c51c0eb32fde7cd20646bfd99625 and determine which gateway or upstream generated the timeout.

The request terminates at 785.097 seconds with:

gateway_stream_timeout
Stream exceeded maximum duration before function timeout

Please check whether the MiMo V2.6 Pro Provider API route has an approximately 785-second maximum streaming duration.

If this limit is imposed by an upstream gateway, please consider routing long MiMo requests through an upstream without this limit, or implementing transparent retry/failover.

Also check why CommandCode Studio records this timed-out request as COMPLETED with 0 input tokens, 0 output tokens, and $0 cost instead of marking it as failed.

Additional context

This has happened several times during one day on the same account - though only this one occurrence is captured.

The timing looks suspicious:
There is a recent Vercel AI Gateway report describing streaming requests being terminated at approximately 785–790 seconds with the same:

gateway_stream_timeout
Stream exceeded maximum duration before function timeout

https://community.vercel.com/t/ai-gateway-streaming-requests-terminate-at-785-790s-despite-a-1800s-function-duration/48725
I don't know whether this CommandCode route uses Vercel AI Gateway or whether this is an equivalent timeout elsewhere in the routing stack, but the timing and error payload appear nearly identical.

Lenguaje dominante
Sin datos de lenguaje
Estrellas
4k
Forks
357
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 CommandCodeAI/command-code

Todos los issues de CommandCodeAI/command-code

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.