investigate(daemon): diagnose idle registration and startup-sweep unit failures
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 25/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- node.js, typescript
- Ambito
- mobile, testing-qa
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- TypeScript
- Stelle
- 5.2k
- Fork
- 359
- Merge medio
- 12h 43m
- PR unite (30g)
- 666
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di callstack/agent-device
-
bug ready-for-agent
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
callstack/agent-device#4018 ·
I maintainer di solito rispondono entro 1 giorno
-
Limrun iOS fill reports success but drops non-ASCII textForse già presa @mvanhorn l’ha presa 9 giorni fa. Apertabug ready-for-agent
Difficoltà 2/5 1-3 ore Idoneità per principianti 87/100
callstack/agent-device#3819 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
callstack/agent-device#1869 ·
I maintainer di solito rispondono entro 1 giorno
-
iOS simulator: snapshot drops controls nested deeper than 64 accessibility levelsForse già presa @KrzysztofMoch l’ha presa oggi. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
callstack/agent-device#4088 ·
I maintainer di solito rispondono entro 1 giorno
-
Limrun network capture: serve tunnel traffic through network dump and a downloadable HAR artifactAperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
callstack/agent-device#4064 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di callstack/agent-device
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
area:desktop area:ui bug platform:macos
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
anthropics/claude-code#106183 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
-
Difficoltà 1/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
core: OpenRouter BYOK sessions record cost = 0 since v2.2.0 (ignores cost_details.upstream_inference_cost)Forse già presa Una pull request collegata a questa issue è aperta o già unita. Apertareproduced
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
anomalyco/opencode#60558 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno