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

Page Stop shows an acceptance card and keeps spending

Ouverte
  • Quelque chose ne va pas ?
#1,350 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

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

Personne n'a encore pris cette issue.

Évaluation

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

Piste de recherche

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.

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

Description

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.

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

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.