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

session: tasks stuck in working on restart, stopped status mapped to failed, and reader handoff

Abierto
#1,554 2 comentarios 0 reacciones 1 asignado 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
68/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
backend, cli

Línea de trabajo

Start with internal/session/task_frontier.go and internal/session/cancel.go to trace startup reconciliation and cancellation status mapping, then read internal/session/read_handoff.go for the reader fallback path. Reproduce restart, cancellation, and failed handoff cases before changing behavior. Done means unfinished tasks are re-queued, explicit cancellation records stopped without retry suggestions, and reader fallback does not leave stopped cards in chat.

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

Descripción

area:session bug sev:serious
Summary

Task frontier state recovery leaves queued tasks hung after restart, stopped tasks are improperly reported as failures, and chat reader subtasks do not fall back cleanly.

Items & Observed Behavior
  1. Tasks hung in working state across restart: A task queued or waiting on machine capacity remains in working status in the database after codeaf engine --stop and restart, but is never re-admitted to the execution frontier.
  2. Stopped tasks mapped to failure: Cancelling a task via x or /stop sets the crew line to failed and outputs /redo stronger... instead of marking it cleanly as stopped.
  3. Chat reader subtask handoff failure: When an inline chat reader subtask fails to hand off, it prints ◆ reading for the chat · stopped and leaves a stopped card in the chat before running inline.
Expected Behavior
  • Engine startup must reconcile persisted task state and re-queue uncompleted tasks onto the frontier.
  • Explicit cancellation (x, /stop) must record status as stopped and omit retry suggestions.
  • Reader subtask handoff failures should fall back to inline reading without polluting the chat stream with stopped task cards.
Root Cause / Location
  • internal/session/cancel.go and internal/session/task_frontier.go: Startup frontier reconciliation and cancellation status mapping.
  • internal/session/read_handoff.go: Silent fallback handling when subtask delegation cannot be completed.

—
Drafted with CodeAF · reviewed and owned by the author

Lenguaje dominante
Go
Estrellas
115
Forks
14
Merge medio
9 h 44 min
PR fusionados (30 d)
766

Preparar el entorno

Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 Agent-Field/CodeAF

Todos los issues de Agent-Field/CodeAF

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.