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

Offen
#65,368 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
30/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
backend

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
227k
Forks
30.7k
Ø Merge
3 Std. 57 Min.
Gemergte PRs (30 T.)
484

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus anomalyco/opencode

Alle Issues in anomalyco/opencode

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.