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

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

Ouverte
  • Quelque chose ne va pas ?
#1,328 0 commentaires 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é
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
42/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
go
Domaine
cli, devtools

Piste de recherche

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.

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

Description

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.

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

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.