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

standing: Only now can do nothing while the card claims done

Abierto
  • ¿Algo no está bien?
#1,611 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

  • #1612 de @santoshkumarradha — cerrado sin fusionar

Evaluación

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

Línea de trabajo

Reproduce the interactive CodeAF chat using the inventory CSV and markdown shopping plan, then trace the approval card through the stand result, execution path, and receipt. Verify that a one-time approval carries the requested action without persistence, that the receipt waits for execution evidence, and that decline and repeating approval retain their stated behavior.

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

Descripción

Defect

Choosing Only now, don't repeat on a repeating standing-task proposal immediately renders done now, nothing kept, even when no work has run. In live DeepSeek v4.1 Flash acceptance, the model then interpreted the answer as a decline and performed no tool call.

Replication

  1. Start an interactive CodeAF chat in a project containing an inventory CSV and a markdown shopping plan.
  2. Ask for a weekly task to read the inventory and refresh the plan without changing inventory or purchasing.
  3. On the approval card select Only now, don't repeat.
  4. The UI claims the work is done immediately. The stand result instructs the model to do an ordinary step but also says the person chose not to repeat; the recorded assistant response said nothing on disk changed and made no work calls.

Observed on #1596 head a955db54e. Original recording, terminal snapshot, transcript and receipt evidence are preserved on Spark. The live tool response was followed directly by a final reply, with zero work calls between them. A subsequent explicit user correction did recover the workflow.

Acceptance

  • Approval for one execution must carry the actual requested action into the execution path, with no repeating arrangement installed.
  • The approval receipt must distinguish authorization from completed execution; do not claim done until there is execution evidence.
  • A real inventory-plan workflow must perform the once-approved refresh without the person having to repeat the instruction.
  • Decline still performs nothing, and normal repeating approval still persists the repeating item.

Related to #1520 prompt/documentation review and discovered during sustained acceptance. Keep the fix separate for coordinated consolidation.

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

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.