Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

A standing firing that changed nothing is logged as landed

Aberta
  • Algo errado?
#1,582 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
65/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
go
Domínio
cli, testing-qa

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
Go
Estrelas
115
Forks
14
Merge médio
8h 27min
PRs com merge (30d)
229

Preparar o ambiente

Ainda não verificamos os arquivos de configuração deste projeto. Comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de Agent-Field/CodeAF

Todas as issues de Agent-Field/CodeAF

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.