Session idle for 40 hours resumed on its own and ran 139 turns

Aperta
#65,368 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
backend

Direzione di ricerca

The reproduction is clear but the cause is not: start by tracing the session lifecycle around the transition to idle, then where a server restart delivers notices to live sessions, and finally how a subagent-completion message is queued and delivered to its parent. The reporter does not know whether the restart notice or the seven-day-stale completion is the trigger, so both paths need reading. Done looks like a test that restarts a server with an idle session and a stale subagent completion and asserts no assistant turns run without a user message.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area/core platform/macos triaging type/bug version/v2

Session idle for 40 hours resumed on its own and ran 139 turns

What happens

A session that had reached idle resumed by itself after 40 hours and ran 139 assistant
turns over 40 minutes. There was no user message in that window. The user was working in a
different session and was not aware this one was running.

The first turn acted on a subagent completion from a subagent session that had finished
seven days earlier, after the user had explicitly stopped it.

Expected

A session that has reached idle has no work in progress. It should not resume without a
user message.

Steps

  1. Let a session reach idle.
  2. Leave it for a long period.
  3. Restart the server.
  4. The session resumes without a user message and runs turns.

Environment

  • opencode v2.3.0
  • macOS (Darwin)
  • No plugins

Additional context

A restart notice was delivered to five sessions 5 seconds before this one resumed. Whether
the restart or the stale subagent completion was the proximate trigger is not known to me.

Whether delayed subagent-completion delivery resuming its parent is intended is also not
known. If it is, the seven-day delay and the 139 unattended turns are still the issue.

Lingua principale
TypeScript
Stelle
227k
Fork
30.7k
Merge medio
3h 57m
PR unite (30g)
484

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di anomalyco/opencode

Tutte le issue di anomalyco/opencode

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.