investigate(daemon): diagnose idle registration and startup-sweep unit failures
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- node.js, typescript
- Área
- mobile, testing-qa
Línea de trabajo
Start with the two failing assertions in src/daemon-entrypoint.test.ts at lines 297 and 364, then read the daemon startup, idle-close, and startup-sweep lifecycle code they exercise. Reproduce each failure separately and record the base/head commands, worker settings, matching assertions, and cleanup; treat races as hypotheses until a trace confirms them. Completion requires a demonstrated lifecycle fix with regression proof and a passing serialized gate at the exact head.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Purpose
Diagnose the daemon-entrypoint failures exposed by the full unit gate while validating a fixture-provenance correction under #4045. Keep this work with the daemon startup/shutdown owner; the fixture correction changes no runtime code.
Observed evidence
At 904c91b3aec56d9869ae535a305dedf8815a81f4, exact affected receipt run-E3Ovk1 failed unit after 16,445 passed, two failed and one skipped:
src/daemon-entrypoint.test.ts:297: “daemon entrypoint reaps itself when idle” exits zero with empty stderr, butdaemon.infostill exists. Expected absent; actual present.src/daemon-entrypoint.test.ts:364: “startup sweep settles a foreign dead owner without touching a live same-named session” exceeds its 5,000 ms test budget.
The four trait suites pass 103 tests. An isolated full-unit comparison at unchanged base 9058a8f4e2a2117448405e03ee4dc7f5488c12af passed 16,447 tests with one skipped, using independent frozen install/build and default workers. A focused observed probe passed eight cases. Neither failure reproduced; no contention or regression cause is established. Diagnostic-only PR #4090 now preserves sanitized failure evidence; its full exact gate passed. A next failing trace is needed before a runtime fix is selected.
Required behavior and completion
- Preserve ownership-fenced detached removal, including deliberate declines, and foreign-owner recovery isolation.
- Record base/head commands, worker settings, matching assertions and cleanup. Separate the two failure causes unless evidence connects them.
- Trace startup publication versus idle close, and the sweep's process-identity/teardown waits. Treat races as hypotheses until reproduced.
- Fix any demonstrated defect at its owning lifecycle/construction boundary. Do not widen timeouts or suppress selection/assertions to obtain a pass.
- Retain meaningful regression proof and validate the resulting exact head through the serialized gate. Source-only diagnostics do not establish a fix.
The orchestrator completed controlled comparisons and cross-provider source assessment. Await a new failing trace at the diagnostic head before selecting a runtime fix. No device run is required unless diagnosis changes live dispatch or native behavior. Do not touch other sessions, devices or worktrees.
- Lenguaje dominante
- TypeScript
- Estrellas
- 5.2k
- Forks
- 359
- Merge medio
- 12 h 43 min
- PR fusionados (30 d)
- 666
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de callstack/agent-device
-
bug ready-for-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
callstack/agent-device#4018 ·
Los mantenedores suelen responder en 1 día
-
Limrun iOS fill reports success but drops non-ASCII textPosiblemente ocupada @mvanhorn la tomó hace 9 días. Abiertobug ready-for-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 87/100
callstack/agent-device#3819 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
callstack/agent-device#1869 ·
Los mantenedores suelen responder en 1 día
-
iOS simulator: snapshot drops controls nested deeper than 64 accessibility levelsPosiblemente ocupada @KrzysztofMoch la tomó hoy. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
callstack/agent-device#4088 ·
Los mantenedores suelen responder en 1 día
-
Limrun network capture: serve tunnel traffic through network dump and a downloadable HAR artifactAbierto
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
callstack/agent-device#4064 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de callstack/agent-device
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
area:desktop area:ui bug platform:macos
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
anthropics/claude-code#106183 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
reproduced
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
anomalyco/opencode#60558 · 1 comentario ·
Los mantenedores suelen responder en 1 día