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

A standing firing that changed nothing is logged as landed

Abierto
  • ¿Algo no está bien?
#1,582 0 comentarios 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
65/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
cli, testing-qa

Línea de trabajo

Start with the /standing item log and reproduce the firing using the provided dev build, isolated profile, and failing Go test repository. Compare the recorded ending with git status and go test ./... after the run, then trace the existing status decision from the standing firing to its log. Done means an unchanged firing is recorded as "nothing changed" or as a failure, never "landed", with an e2e check covering it.

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

Descripción

area:session bug sev:serious

Seen on: dev 837b2b0.

Behaviour

A standing watch fired, made no edits and left the tests red, but its item log showed landed. A firing that did nothing should say so, not landed. Related to #1550 (a firing's claim is not checked against the repo).

Replication

  1. Build dev 837b2b0 (git checkout 837b2b0 && make build, binary bin/codeaf), or install the dev build with curl -fsSL https://agentfield.ai/get/devaf | bash.
  2. Use an isolated profile: export HOME=$(mktemp -d), export OPENROUTER_API_KEY, and keep the default model (~deepseek/deepseek-v4-flash-latest, crew on auto).
  3. On a busy machine set task.max_load to 0 (/settings, Tasks) so the busy-machine gate does not hold tasks.
  4. Make a Go repo with a failing test: R=$(mktemp -d) && cd "$R" && git init -q && printf 'package main\n\nfunc main() {}\n' > main.go && printf 'module demo\n\ngo 1.22\n' > go.mod && git add -A && git commit -qm init, add a failing _test.go, commit.
  5. codeaf, then: Every 2 minutes run go test ./... here; if a test fails, fix it. Accept the standing card with 1.
  6. After a firing, read /standing (the item's log) and git status / go test ./....

Evidence

  • Item log: landed for a firing with no edits; tests still red afterwards.
  • Code path not traced in this pass.

Guessed cause

A guess from reading the code, not a confirmed diagnosis. The firing's ending is taken from the run's own report rather than from the repo's state after the run.

Acceptance

  • e2e: a firing that made no change logs nothing changed (or the failure), never landed.

Found while writing the public docs; manual text differences are in #1545.

🤖 Generated with Claude Code

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

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.