Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Dollar limit leaves codeaf do pending until the deadline

Offen
  • Stimmt etwas nicht?
#1,353 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
72/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
go
Bereich
cli, documentation, testing-qa

Rechercherichtung

Start with settlementWatch.wait and settlementWatch.saySomethingIfQuiet in cmd/codeaf/do.go, then trace TaskReasonOf in internal/session/task_status.go to understand how pending work and budget stops are resolved. Run the described e2e and unit scenarios with stub cost accounting, and inspect internal/manual/chat/running-from-the-terminal.md and models-and-cost.md. Done means exhausted dollar limits produce prompt budget stops while higher limits start the task, with matching documentation and change-entry metadata.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area:headless bug sev:serious

What happened

PRE-EXISTING defect seen on commit 17ae56d34 (staging-20260921-17ae56d3496f) on 2026-09-21 and also on v0.3.0 (9258f7052). Lane A2, item A2-05, set both daily_budget_usd and CODEAF_MAX_COST to 0.001. codeaf do then sat at:

1 task pending, none running

Staging exited 3 after 300 seconds with JSON fields "spend": 0.003388978, "spend_work": 0, "stop": "deadline", and "answer": "The time limit was reached before anything finished...". v0.3.0 behaved the same after 240 seconds. Neither named the dollar limit.

Replication

Deterministic (no model).

No no-model reproduction is established; lane A2 reproduced the blocked launch with live accounting.

Field (real models).

Set OPENROUTER_API_KEY, then prepare a fresh home and repository:

root="$(mktemp -d)"; export CODEAF_HOME="$root/home"; repo="$root/repo"
mkdir -p "$CODEAF_HOME" "$repo" && printf '{"daily_budget_usd":0.001}\n' > "$CODEAF_HOME/config.json"
git -C "$repo" init -q
git -C "$repo" -c user.name=Test -c [email protected] commit --allow-empty -m base
CODEAF_MAX_COST=0.001 codeaf do "write numbers 1 to 3000 into numbers.txt one per line, using a bash loop that sleeps 1 second after each number" --dir "$repo" --yes-spend --json --model deepseek/deepseek-v4-flash --timeout 5m

Today stderr says 1 task pending, none running; after five minutes JSON says "stop":"deadline" and the process exits 3.
Budget five minutes and about $0.01. Repeat with a comfortably higher daily and run limit as the control; the task should start instead of remaining pending. v0.3.0 has the same low-limit defect.

Where

The terminal receipt and quiet-wait paths are settlementWatch.wait and settlementWatch.saySomethingIfQuiet in cmd/codeaf/do.go; the task stop reason is exposed by TaskReasonOf in internal/session/task_status.go. The evidence does not establish why the pending state wins over the budget stop.

The fix

If the daily or run dollar limit prevents all pending work from starting, settle immediately as a dollar-limit stop. JSON must use "stop":"budget" and the answer must say a dollar limit you set stopped it; do not wait for --timeout and call it a deadline.

Acceptance

  • e2e: Through codeaf do --json with a stub cost ledger already beyond CODEAF_MAX_COST=0.001, assert prompt exit 3, "stop":"budget", answer text a dollar limit you set stopped it, and no deadline value.
  • e2e: Through the same door with a higher limit, assert the stub task leaves pending, enters running, and the result is not stopped for budget.
  • Unit: A settlement with pending work, no running work, and an exhausted daily or run dollar allowance maps to budget immediately and cannot later map to deadline.
  • The manual pages internal/manual/chat/running-from-the-terminal.md and internal/manual/chat/models-and-cost.md quote the budget-stop wording and JSON field, and the change entry's invalidates names the old belief that an unstartable dollar-limited task should wait for the time wall.

Filed from the 2026-09-21 staging verification of 17ae56d34; the lane reports, frames and e2e logs are in the owner's handoff folder for this promotion.

Vorherrschende Sprache
Go
Sterne
115
Forks
14
Ø Merge
9 Std. 38 Min.
Gemergte PRs (30 T.)
749

Entwicklungsumgebung

Die Einrichtungsdateien dieses Projekts haben wir noch nicht geprüft. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus Agent-Field/CodeAF

Alle Issues in Agent-Field/CodeAF

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.