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

a worker was handed no note at all under a loaded full-tree run

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
52/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
go
领域
testing-qa

调研方向

Start with TestTwoWorkersLiveAtOnceEachGetOnlyItsOwnNote in internal/run/note_channel_test.go and reproduce the package with -race, then compare it with the full-tree run described at commit 2f94ca1f0. Trace the two workers' note delivery decisions and improve the failure output to identify each worker's notes and timing. Done means the runtime or fixture issue is fixed, the change explains which it was, and package -race covers it in CI.

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

描述

area:tests bug sev:papercut

What happened

TestTwoWorkersLiveAtOnceEachGetOnlyItsOwnNote in internal/run failed once,
inside a run of 112 packages at once on a loaded build box.

--- FAIL: TestTwoWorkersLiveAtOnceEachGetOnlyItsOwnNote (0.66s)
    note_channel_test.go:326: alpha was handed its own note 0 times, want once
FAIL	github.com/Agent-Field/codeaf/internal/run	29.998s

The dump the assertion prints shows three requests to alpha, each carrying the
work order and the ask, and none of them carrying the note. So the note was not
delivered late or delivered to the wrong worker in that run. It was not there at
all across every request the worker made.

It does not reproduce, and that is the report

Sixteen attempts on the same tree at the same commit, on a box at load 0.33:

what result
-count=5 -run TestTwoWorkersLiveAtOnce ./internal/run/ ok 2.758s
-count=3 ./internal/run/ (whole package, so the other tests run beside it) ok 75.353s
GOMAXPROCS=1 -count=8 -run TestTwoWorkersLiveAtOnce ./internal/run/ ok 4.151s

Filing rather than rerunning is deliberate. The repository's own rule is that a
test failing only when other suites run beside it is a bug report and not a
known shape, and this test is about two workers being live at once, which is the
condition a loaded box actually supplies and an isolated rerun does not.

It is NOT in .github/known-red.txt and must not be added to it.

Why it matters more than an ordinary flake

The behaviour under test is the one #1356 shipped: a note is a channel into a
running worker rather than a log nobody reads. A worker that never receives its
note is that feature not working, and the failing case renders exactly like a
run where nobody sent a note. If this is real, the product symptom is silence.

Replication

Not reliable. What produced it once: go test -count=1 over every package
except internal/tui3 and internal/session on one box, roughly 112 packages,
during a full-tree check. The commit was 2f94ca1f0.

Acceptance

  1. Whatever the cause, the test's failure output says which of the two workers
    got which notes and when, not only that alpha got none. The current dump
    shows the requests but not the delivery decisions, so a reader cannot tell a
    note that was never written from one written to the wrong worker.
  2. If it is a race in the runtime, -race on this package in CI names it.
  3. If it is a race in the fixture, the fixture is fixed, and the change says
    which of the two it was. Not "made deterministic".
主要语言
Go
星标
115
派生
14
平均合并
9 小时 44 分钟
30 天内合并 PR
766

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 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 摘要。