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

🤖 bug: a workflow plan task with an empty plan file may never get its completion prompt

Cerrado
  • ¿Algo no está bien?
#4,454 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend, testing

Línea de trabajo

Start with taskService.reportDecisionHold.test.ts and the real-host test described in #4450, using a workflow plan task with no plan file. Exercise the path through handleStreamEnd and handleSuccessfulWorkflowProposePlan. Done means the test establishes whether the completion prompt is admitted; if it fails, the decision is resolved as a non-report before that prompt.

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

Descripción

Summary

Suspected, not yet reproduced. A workflow-owned plan task whose propose_plan succeeds but whose plan file is missing or empty may never get its completion prompt. It would stay awaiting_report until a timeout or restart.

Why we suspect it

This is the same mechanism as the plan auto-handoff kickoff bug fixed in #4450:

  1. When a task's stream ends, handleStreamEnd resolves the stream-end decision as a non-report before its recovery sends. It skips that step when the task is plan-like and propose_plan succeeded, because for a workflow plan task that result is normally the report.
  2. handleSuccessfulWorkflowProposePlan then finds no plan content and calls promptTaskForRequiredCompletionTool instead. At that point the ended stream's decision is still pending.
  3. The prompt's admission token (minted by the caller since #4450, or by WorkspaceService.sendMessage on main) treats a pending decision for its attempt as stale. If the session is idle, the send is therefore refused with "the target was stopped or interrupted while the message was being admitted".

For the non-workflow handoff, #4450 confirmed this chain with a real-host test that fails on main. This path has no such test yet.

Next step

Write a real-host test like the one in #4450 (taskService.reportDecisionHold.test.ts, "plan-handoff kickoff on the real host"), using a workflow plan task with no plan file. If the test fails, resolve the decision as a non-report before that prompt.

Owner: the workflow-recovery follow-ups workspace (the owner of #4414 and G2).

Related

#4450, #4414, #4308.

Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high

Lenguaje dominante
TypeScript
Estrellas
2.1k
Forks
140
Merge medio
4 h 58 min
PR fusionados (30 d)
905

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

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 coder/xum

Todos los issues de coder/xum

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.