mirror of
https://github.com/MoonshotAI/kimi-code.git
synced 2026-08-30 12:32:34 +00:00
fetch() was issued with no signal anywhere, so a hung connection (the half-open TCP you get after a network change — the same scenario that kills the WS) left the promise pending for minutes. submitPrompt sets the per-session in-flight flag before awaiting, and that flag is only cleared on settle, so one hung submit silently routed every subsequent prompt into the queue until the browser's own socket timeout fired. AbortSignal.timeout(30s) turns the hang into the existing DaemonNetworkError path (with a jsdom-safe fallback), which already cleans up the in-flight state. |
||
|---|---|---|
| .. | ||
| kimi-code | ||
| kimi-web | ||
| vis | ||