Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

a failed landing with its work kept asks forever, long after nothing is waiting on the answer

Aperta
  • Qualcosa non va?
#1,328 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
42/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go
Ambito
cli, devtools

Direzione di ricerca

Start at internal/session/task_status.go:441 and trace how TaskFailed with Held facts becomes ProjectTask status and contributes to needs you. Compare the recorded later nodes, branch existence, and continuation evidence to decide when the conversation has moved past a held landing. Done means the card retains its branch and offer while no longer marking or counting a non-blocking demand.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area:session bug sev:serious

What happens

A task that ends failed with its work still held keeps wearing your call and keeps counting toward needs you, for the rest of the session, with no way to reach zero except answering each one.

internal/session/task_status.go:441:

case TaskFailed:
	if facts.Held {
		// THE ANSWER IS STILL THERE AND SOMEBODY MAY STILL WANT IT...
		status.Presence, status.On = TaskPresenceNeedsLook, TaskWaitPerson
		return status
	}

The offer is real — the branch is on disk and taking it anyway is a genuine answer. The problem is that the offer never expires.

What it looks like

One session, 23 nodes. Four rows stand in needs you, all state=failed, ending=refused, merge=aborted, each with a kept branch that exists:

node title branch
4 Skills: five-part record and store serving task/skills-five-part-record-and-stor-…
6 Skills: chat shelf and use_skill tool task/skills-chat-shelf-and-use-skill-…
7 Store skill fact fields task/store-skill-fact-fields-…
15 File GitHub issue: standing firing sees empty task board task/file-github-issue-standing-firin-…

By the time they were read, the conversation had moved two tranches past them: a later node had already landed a continuation of the same store-record branch, none of the four branches had ever been pushed, and nothing in flight was waiting on any of them. The count said four people-shaped questions. Zero of them were blocking anything.

Why it is wrong

A mark exists only when a person's answer is the one thing unblocking the work. A card may keep showing a state; a mark must not. A mark is a demand and a card is a status. Four standing demands that unblock nothing train a person to stop reading the count, which costs the marks that do matter.

Shape of the fix

A held landing is a question while the conversation is still on it, and a status afterwards. When the work has been superseded, or the session has moved past it, the row keeps its branch and its offer on the card and stops wearing the mark and stops counting toward needs you.

Open question for whoever takes it: what "moved past it" should be measured against. Candidates seen here — a later node that landed the same branch, a node whose branch no longer exists, and plain distance in the graph. The first two are facts already on the record; the third is a guess. Pick from the record, not the clock.

Not this

The four rows are not stale state, not a cache, and not a surface drawing something the engine did not say. This was checked: the engine was restarted onto the current build first, the records were read off disk, and the rows are what ProjectTask returns for those facts. The reading is correct. The demand is what is wrong.

Lingua principale
Go
Stelle
115
Fork
14
Merge medio
9h 37m
PR unite (30g)
755

Preparare l'ambiente

Non abbiamo ancora controllato i file di configurazione di questo progetto. Parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Agent-Field/CodeAF

Tutte le issue di Agent-Field/CodeAF

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.