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

Page Stop shows an acceptance card and keeps spending

Offen
  • Stimmt etwas nicht?
#1,350 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
68/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
go
Bereich
cli, testing-qa

Rechercherichtung

Start at app.taskPlanStopTaken in internal/tui3/taskplan.go, then follow Agent.CancelWithReason in internal/session/cancel.go and Agent.settleUnfinished in internal/session/task_run.go. Run the page-stop reproduction in tmux and inspect the e2e and unit acceptance requirements. Done means stopped runs settle once, reject checking, acceptance, and resume, use no new model resources, and the manual and change-entry updates are present.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area:chat area:session bug sev:serious

What happened

NEW PRESENTATION defect seen on commit 17ae56d34 (staging-20260921-17ae56d3496f) on 2026-09-21. Lane A1, item A1-05, stopped a running task from its page. The row said slow counting loop stopped, but the page then showed:

a accept  n not right  s tell it
Working checking

Tokens, cache, and spend continued rising. On v0.3.0 (9258f7052), post-stop spending and automatic resumption were already present, so that part is PRE-EXISTING; the acceptance card after page Stop is new.

Replication

Deterministic (no model).

No no-model reproduction is established; lane A1 reproduced the extra presentation and spend with a live run.

Field (real models).

Set OPENROUTER_API_KEY, then start a fresh local chat:

root="$(mktemp -d)"; export CODEAF_HOME="$root/home"; repo="$root/repo"
mkdir -p "$CODEAF_HOME" "$repo" && git -C "$repo" init -q
git -C "$repo" -c user.name=Test -c [email protected] commit --allow-empty -m base
cd "$repo" && codeaf chat --no-host --yolo --model deepseek/deepseek-v4-flash

Enter /task count slowly from 1 to 2000, sleeping one second between numbers, open its page, choose Stop, and watch the status and spend for 30 seconds. Today stopped is followed by a accept n not right s tell it, Working checking, and rising spend.
Allow about three minutes and $0.05. The v0.3.0 control uses the same steps: it may keep spending after stop, but does not show the acceptance card.

Where

The page-stop and settlement seams are app.taskPlanStopTaken in internal/tui3/taskplan.go, Agent.CancelWithReason in internal/session/cancel.go, and Agent.settleUnfinished in internal/session/task_run.go. The evidence does not establish which transition emits the extra turn.

The fix

Page Stop is terminal for that run. Once the row says stopped, do not open a accept n not right s tell it, do not enter Working checking, do not automatically resume, and stop new model usage for the run.

Acceptance

  • e2e: Through a run page in tmux codeaf chat --no-host, stop a stub long-running task and assert stopped appears while a accept n not right s tell it and Working checking never appear, then exit 0.
  • e2e: Through the same page with metered fake receipts, assert token, cache, and spend fields remain unchanged for ten seconds after stopped.
  • Unit: Every transition caused by taskPlanStopTaken settles unfinished work once and rejects later checking, acceptance, or resume transitions for that run.
  • The manual page internal/manual/chat/task-controls.md says page Stop is terminal, and the change entry's invalidates names the old belief that a stopped run could still enter checking or acceptance.

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. 44 Min.
Gemergte PRs (30 T.)
775

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.