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

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

Aperta
  • Qualcosa non va?
#940 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

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

Direzione di ricerca

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.

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

Descrizione

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.

Lingua principale
Nessun dato sulla lingua
Stelle
4k
Fork
357
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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

Tutte le issue di CommandCodeAI/command-code

Issue simili

Altre issue su Backend & API Design

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.