GCWing / GCWing/OpenBitFun

[Bug]: queued chat messages fail visibly when the session turns busy during queue drain

Cerrado
#2,660 0 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Rust
Estrellas
2.3k
Forks
231
Merge medio
2 h 49 min
PR fusionados (30 d)
589

Descripción

## Summary

When startTurn finds the state machine non-IDLE it throws "Session is still busy finishing the previous turn..."; sendMessage surfaces this as a "Thinking process error" toast and drainPendingQueue marks the queued item failed, even though the situation is transient (the session was revived busy after the drain gate confirmed IDLE). The thrown error is now tagged isSessionBusy; sendMessage drops the optimistic turn and re-throws without toasting, and drainPendingQueue silently re-queues the item so auto-drain reapplies once the session returns to IDLE. Includes a regression test for the silent re-queue path.

## Area

src/web-ui/src/flow_chat/session-drivers/local/LocalSessionDriver.ts + src/web-ui/src/flow_chat/services/flow-chat-manager/MessageModule.ts (+ MessageModule.test.ts).

## Reproduction or evidence

At 32f2427697, LocalSessionDriver.ts :372 throws the still-busy error without any marker, MessageModule.ts :613 marks drained items failed, and :484 shows the error toast; there is no isSessionBusy symbol anywhere in the flow_chat tree (Grep zero hits). Regression test asserts the queued item is re-queued (not failed), no toast is shown, and the item is not removed.

## Environment

All platforms (frontend queue/driver); baseline 32f2427697.

---
AI-assisted change. Testing: verified locally (`pnpm vitest run MessageModule.test.ts` 27 passed, 0 failed, including the new regression case; `pnpm run type-check` (tsc --noEmit) exit 0 with no errors).

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza en src/web-ui/src/flow_chat/session-drivers/local/LocalSessionDriver.ts y src/web-ui/src/flow_chat/services/flow-chat-manager/MessageModule.ts, siguiendo startTurn, sendMessage y drainPendingQueue. Ejecuta pnpm vitest run MessageModule.test.ts y verifica que una condición transitoria de busy vuelva a poner el elemento en la cola sin mostrar un toast ni eliminarlo, mientras pnpm run type-check finaliza correctamente.

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

Evaluación

Stack tecnológico
typescript
Área
frontend, testing
Tipo de issue
Error
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Activo
Claridad
Bien especificado
Aptitud para principiantes
82/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.