Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
  • 哪里不对？
#1,328 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
42/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
go
领域
cli, devtools

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Go
星标
115
派生
14
平均合并
9 小时 37 分钟
30 天内合并 PR
755

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

Agent-Field/CodeAF 的其他 Issue

查看 Agent-Field/CodeAF 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。