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

Abierto
#65,368 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
227k
Forks
30.7k
Merge medio
3 h 57 min
PR fusionados (30 d)
484

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de anomalyco/opencode

Todos los issues de anomalyco/opencode

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.