Hacktoberfest 2026: những issue maintainer đã đánh dấu cho tháng Mười, đang mở và phù hợp người mới. Xem issue Hacktoberfest

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

Đang mở
  • Có gì không ổn?
#1,328 0 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
42/100
Loại issue
Lỗi
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
go
Lĩnh vực
cli, devtools

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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.

Ngôn ngữ chính
Go
Star
115
Fork
14
Merge trung bình
9 giờ 37 phút
Pull request đã merge (30 ngày)
755

Chuẩn bị môi trường

Chúng tôi chưa kiểm tra các tệp thiết lập môi trường của dự án này. Hãy bắt đầu từ README và xem hướng dẫn đóng góp lần đầu của chúng tôi để biết các bước chung.

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của Agent-Field/CodeAF

Tất cả issue của Agent-Field/CodeAF

Issue tương tự

Thêm issue về Go

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.