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

chat: a slow engine answer says the task could not start while it runs

未关闭
#1,528 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
75/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
go
领域
backend

调研方向

Start in internal/remote/callclass.go by searching for “did not answer in time,” then trace the chat task-start path through Task.Start. Run or add the deterministic engine-road late-answer test described in the issue. Done means the late response is not reported as a start failure, the surface avoids “could not start,” and the e2e case leaves exactly one task.

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

描述

area:chat bug sev:serious

What happened

On 2026-09-25, on a box at load about 23, starting a /task in the chat printed:

could not start the task · the engine did not answer in time

The task had been created, and it ran to the end. A person who believes the refusal starts it again, and pays for two. This hasn't been reproduced on an unloaded box.

Where

The late-call wording in internal/remote/callclass.go (search did not answer in time), and the chat's task start over the engine road (Task.Start).

Replication

Deterministic: an engine-road test where the engine accepts Task.Start but answers after the surface's deadline. Today the surface says the task could not start, while the store holds a running task.

The fix

A start whose answer is late is not reported as a failure. The surface says the engine is slow to answer — the task may already be running, and then shows the task if it appears. Alternatively, the start is made idempotent, so a retry does not duplicate it.

Acceptance

  • e2e: with a late engine, one task exists, and the surface never says could not start.
  • Unit: the late-answer classification for Task.Start does not map to a start failure.
主要语言
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 摘要。