Late-recall regression reports recall instead of recall:late in combined gate

未關閉
  • 哪裡不對？
#1,655 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

  • #1656 來自 @santoshkumarradha —— 已關閉，未合併

評估

難度
4/5
預估耗時
3-5 天
新手友好度
58/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
go
領域
backend, testing-qa

研究方向

Start with internal/session/loop_speed_test.go, TestARecallThatLandsAfterTheFirstWordRidesTheNextStep, and its paceCompleter/paceAgent fixture; run the isolated test at the published commit. Trace the production recall/first-word boundary and determine whether the fixture’s ordering is guaranteed or racing. Done means an evidenced before/after cause, preserved assertions, a passing session suite, and a passing combined gate without sleeps or skips.

由索引模型根據 Issue 內容生成。

描述

area:session bug sev:papercut

What happened

The independent combined gate for PR #1632 at 458d1be73b513f2b43afebaa544677ac5353d365 failed one session regression on 2026-09-28:

TestARecallThatLandsAfterTheFirstWordRidesTheNextStep
loop_speed_test.go:421: the decomposition names [recall], want the block written down as late
--- FAIL: TestARecallThatLandsAfterTheFirstWordRidesTheNextStep (0.67s)

The session package failed one of eight shards; the eight interface shards and all seven other affected packages passed. Build, static analysis, manual/change-entry checks and all law checks passed. GitHub CI passed the same commit (run), so this observation must not be described as a deterministic reproduction or dismissed as a passing rerun. The independent gate exited 2.

Replication

No model calls are required. Check out the exact published commit, then run the observed gate:

git checkout 458d1be73b513f2b43afebaa544677ac5353d365
GOMAXPROCS=4 GOFLAGS=-p=2 make pr-ready BASE=b267d390078494f659ade14fe8b31daee255771a

The existing fixture can be selected for investigation with:

GOMAXPROCS=4 GOFLAGS=-p=2 go test -count=1 -timeout 15m ./internal/session -run '^TestARecallThatLandsAfterTheFirstWordRidesTheNextStep$'

Its isolated failure frequency has not yet been measured. The fixture emits the first word, delays its first response by 400ms, and requests recall with a 100ms delay. Determine whether the ordering assumed by the fixture is guaranteed before attributing the failure to scheduling or changing runtime behavior.

Where

internal/session/loop_speed_test.go, TestARecallThatLandsAfterTheFirstWordRidesTheNextStep, the paceCompleter/paceAgent fixture and the production recall/first-word boundary they exercise.

Expected behavior and acceptance

  • Through the real session submission path with its scripted completer, recall that arrives after the first emitted word is recorded as recall:late, does not cut/re-ask that response, and appears in the next request.
  • Preserve all three existing assertions. Use explicit ownership/order synchronization if the fixture is racing; do not merely enlarge sleeps, waive the test or add it to a skip list.
  • Establish a before/after reproduction for the actual cause, then pass the affected session suite and combined gate on the corrected revision.
  • If investigation finds a user-visible runtime defect, verify the corresponding ordinary workflow and update its manual/change entry. No separate live user-facing recall failure has been established yet.

Batch boundary

The owner froze #1632 and requested an honest review handoff with this failing independent gate disclosed. This issue belongs to the next batch; do not add its fix to the frozen #1632 revision.

主要語言
Go
星號
115
分支
14
平均合併
10 小時 36 分鐘
30 天內合併 PR
450

環境準備

我們還沒有檢查這個專案的環境設定檔。先看它的 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 摘要。