Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#1,528 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
75/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
go
Domínio
backend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
Go
Estrelas
115
Forks
14
Merge médio
9h 44min
PRs com merge (30d)
775

Preparar o ambiente

Ainda não verificamos os arquivos de configuração deste projeto. Comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de Agent-Field/CodeAF

Todas as issues de Agent-Field/CodeAF

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.