[Bug] A resumed session stream closes before a queued message is drained, so the answer never reaches the client
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 55/100
- Issue-Typ
- Bug
- Klarheit
- Klar beschrieben
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- typescript
- Bereich
- backend, distributed-systems
Rechercherichtung
Start with packages/local-runtime-v2/src/application/conversation/conversation-application.ts and packages/local-runtime-v2/src/service/session-system/stream/session-stream-service.ts, tracing how resumed streams decide liveness and handle terminal events. Check the active-turn source and the replay boundary; done means a resumed live stream delivers the queued turn's answer, clears its queue row, and a stream following an ended turn closes at the replay point.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Title
A resumed session stream closes before a queued message is drained, so the answer never reaches the client
Where
packages/local-runtime-v2/src/application/conversation/conversation-application.ts
and packages/local-runtime-v2/src/service/session-system/stream/session-stream-service.ts
Reproduction
- Start a session and let a turn run.
- While it runs, queue a message.
- Reload the client, so it resumes the session.
- The queued message drains and its answer is produced, but the client never
sees it, and the queue row is not cleared.
Why
Two defects stack.
The liveness check reads a lagging projection. Whether a resumed stream
is live or replay-only is decided from the session's persisted status, and
that status is an asynchronous projection of the state events. While a turn
is still running it can read as idle. The runtime then hands the client a
replay-only stream that closes, and the answer committed later never reaches
it. The runtime contradicts itself: asked "is there an active turn?" it says
yes, and in the next moment it says idle.
The authoritative answer is the active turn itself.
The stream waits for a terminal event that will not come. A stream that
follows a turn that has already ended waits for that turn's terminal event,
which was published before the client attached. The wait never resolves, so
the stream hangs instead of ending at the replay point.
The stream has to remember which turn the last terminal event belonged to,
and end at the replay point when it follows a turn that already ended.
Impact
Every client that resumes a session is affected, not only the WebUI. The
user sees a queued message that never gets an answer and a queue row that
never clears.
Expected
- the liveness decision uses the authoritative active turn
- a stream that follows an already-ended turn ends at the replay point
instead of waiting forever
Notes
The client can re-read the transcript and the queue once its event channel is
ready, and that covers the projection the client holds. It cannot cover the
frame itself: the browser's event channel carries lifecycle events only, and
the live stream frames travel on their own connection. The client also must
not set the "drain queued" flag on its own, because that flag starts the
queued turn as a side effect.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 2k
- Forks
- 259
- Ø Merge
- 11 Std.
- Gemergte PRs (30 T.)
- 81
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus MiniMax-AI/minimax-code
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
MiniMax-AI/minimax-code#507 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug needs-triage tui
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
MiniMax-AI/minimax-code#481 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug cli documentation needs-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
MiniMax-AI/minimax-code#299 · 3 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 55/100
MiniMax-AI/minimax-code#526 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 57/100
MiniMax-AI/minimax-code#525 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in MiniMax-AI/minimax-code
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
braintrustdata/braintrust-sdk-javascript#2659 ·
Maintainer antworten meist innerhalb von 1 Tag
-
body-parser 2.3.0 in the published ai-dial-chat-bff image is vulnerable (CVE-2026-111181, HIGH)Evtl. vergeben @illya-havsiyevych hat das heute übernommen. Offenbug
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 87/100
epam/ai-dial-chat#9566 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 83/100
Maintainer antworten meist innerhalb von 1 Tag
-
はさみアイコンを修正するOffenbug
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 68/100
-
resource.reload() while params is in error switches the resource to 'idle' instead of retryingOffenarea: core
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
Maintainer antworten meist innerhalb von 1 Tag