Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

daemon start reports DAEMON_CONNECTION_LOST for a daemon that never came up

Cerrado
  • ¿Algo no está bien?
#684 2 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@V3RON ya está trabajando en esto.

Desde el 18/10/2026.

  • #710 de @V3RON — fusionado

Evaluación

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

Línea de trabajo

Start by reading the auto-launch polling path in src/cli/index.ts:239 and the HTTP-start failure path in src/daemon/main.ts:660; compare the error definitions in docs/CLI.md:132 and :498, and review the related discussion in #672. Done means auto-launch failures, including a daemon that stops before becoming available, are reported consistently as failed starts rather than as a lost live connection.

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

Descripción

bug:ready

simlock daemon start sometimes reports DAEMON_CONNECTION_LOST for a daemon that never came
up, instead of a failed start.

With the daemon's HTTP port held by another process (so the daemon claims its unix socket,
answers the CLI's hello, then stops itself on http-start-failed at
src/daemon/main.ts:660), most runs report the auto-launch timeout, and some report:

{"error":{"code":"DAEMON_CONNECTION_LOST","message":"Daemon connection closed"}}

exit 1, after ~240 ms. 4 of 22 direct daemon start runs at 24ce3d5a took that shape, plus
one of three console-lane runs (worker mode, fake driver, the daemon's HTTP port held); the rest
gave Timed out starting simlock daemon.

docs/CLI.md:132 defines that code as "the thing you were talking to went away" and
docs/CLI.md:498 as a live connection that died, leaving the lease standing. daemon start
never had a daemon to lose, so the line names no fact about the start: it reads as though a
running daemon died under the command. A script cannot tell a failed start from a lost daemon.

The connection is the CLI's own poll hitting the socket in the window before the dying daemon
releases it (src/cli/index.ts:239), so which of the two lines a start reports is left to
timing. Twice on a build of bd664e22 the same start instead exited 13 with
Warning: Detected unsettled top-level await and no cause; it did not reproduce on a build of
the tip. #672 already disputes the code the timeout path reports; a fix that classifies
auto-launch failures should cover these paths too.

Found while triaging #673.

Written by an agent.

Lenguaje dominante
TypeScript
Estrellas
20
Forks
2
Merge medio
8 h
PR fusionados (30 d)
316

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 callstackincubator/simlock

Todos los issues de callstackincubator/simlock

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.