Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Checker spend ceiling is shared by the whole run, and the run still says done

Ouverte
  • Quelque chose ne va pas ?
#1,572 0 commentaires 0 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@santoshkumarradha y travaille déjà.

Depuis le 27/9/2026.

  • #1604 par @santoshkumarradha — fermée sans fusion

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
55/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
go
Domaine
backend, cli

Piste de recherche

Start with internal/config/crewspend.go:100-125 and internal/session/taskcrew.go:560, then reproduce the documented multi-part run using the dev build and inspect its plandb check rows. Trace how checker ceilings are assigned and how failed checks affect the landing summary. Done means each check has its own ceiling and any unfinished check prevents a done status and is named in the landing line.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

area:session bug sev:critical

Seen on: dev 837b2b0.

Behaviour

In a fan-out run, most per-part checks end failed: the check stopped at its spend ceiling of $0.75, three times its estimate, before it finished: 16 of 20 checks (run 1) and 9 (run 2) in one lane, 5 of 8 and 93 of 100 in another. Each run still ended done, and the summary read "All 20 issues … done". A check that could not finish is not a passed check, and the ceiling reads as per check but behaves as one pool for the run.

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 small repo with many parts: 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, then create 20 small Go files issue_01.go … issue_20.go, each with one trivial function and a failing test, and commit.
  5. codeaf, then /task Fix every failing test, one part per file issue_NN.go, with a check on every part.
  6. When the run lands, read its plan store (plandb list in the run, or the tasks table of the run's plandb.db): count check: rows with failed: the check stopped at its spend ceiling. Compare with the run's landing line.

Evidence

  • Check rows: failed: the check stopped at its spend ceiling of $0.75, three times its estimate, before it finished (16/20, 9/20, 5/8, 93/100 across four runs); every run ended done.
  • internal/config/crewspend.go:100-118: CrewSeatCeilings returns one ceiling for the crewroute.Checker seat ("THE CEILING BELONGS TO THE SEAT"); crewspend.go:125 is the sentence.
  • internal/session/taskcrew.go:560: SeatCeilings: config.CrewSeatCeilings(d) is set once per crew, so every check in the run draws from it.

Guessed cause

A guess from reading the code, not a confirmed diagnosis. The seat ceiling is keyed per run (the checker seat), not per check, so later checks find it spent. Failed checks are not counted in the landing summary, so the run reports done.

Acceptance

  • e2e: the 20-part run above ends with every check either holding or failing on its own merits; no check ends at a ceiling set for another part.
  • e2e: a run with any check that did not finish does not end done; its landing line names the unfinished checks.

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

🤖 Generated with Claude Code

Langage dominant
Go
Étoiles
115
Forks
14
Merge moyen
16 h 30 min
PR mergées (30 j)
238

Préparer son environnement

Nous n'avons pas encore vérifié les fichiers d'installation de ce projet. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Agent-Field/CodeAF

Toutes les issues de Agent-Field/CodeAF

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.