Long successful startup consumes the daemon idle timeout and exits before activation polling #415

Closed
opened 2026-10-23 02:23:57 +02:00 by buildagent · 1 comment
Member

Observed on code-index 0.41.10, e3-16/16.0 (Windows), reported through the development channel by its operator agent:

  • 23:39:14 UTC: full extraction begins.
  • 23:43:14: extraction complete; resolving generation 5, 24,913 files.
  • 00:17:37: generation promoted and resolution complete.
  • 00:21:25.363: initial reconciliation complete; watcher armed, parse_count 0.
  • 00:21:26.079: activation poll armed.
  • 00:21:26.096: idle timeout reached (1800s); clean exit at .391.

An approval change made during startup had not yet reached the activation poll. No next-start outcome has been measured.

Source inspection: ServerHandle.last_activity starts at bind and tracks authenticated RPC frames. The steady-state loop checks that old clock immediately after the successful initial reconciliation, and can exit on its first idle tick before the first activation tick. Successful initial reconciliation and successful activation re-arm should establish a fresh idle window; explicit shutdown and degraded-startup policy should remain intact.

Related: #412 (unnecessary extraction after release-label changes), #410 (bounded package-only invalidation). This is a separate lifecycle defect.

Observed on code-index 0.41.10, e3-16/16.0 (Windows), reported through the development channel by its operator agent: - 23:39:14 UTC: full extraction begins. - 23:43:14: extraction complete; resolving generation 5, 24,913 files. - 00:17:37: generation promoted and resolution complete. - 00:21:25.363: initial reconciliation complete; watcher armed, parse_count 0. - 00:21:26.079: activation poll armed. - 00:21:26.096: idle timeout reached (1800s); clean exit at .391. An approval change made during startup had not yet reached the activation poll. No next-start outcome has been measured. Source inspection: ServerHandle.last_activity starts at bind and tracks authenticated RPC frames. The steady-state loop checks that old clock immediately after the successful initial reconciliation, and can exit on its first idle tick before the first activation tick. Successful initial reconciliation and successful activation re-arm should establish a fresh idle window; explicit shutdown and degraded-startup policy should remain intact. Related: #412 (unnecessary extraction after release-label changes), #410 (bounded package-only invalidation). This is a separate lifecycle defect.
Author
Member

Confirmed by a real-binary regression using the existing reconcile-delay hook: startup delayed 61 seconds with --idle-min 1 and no RPC traffic. With the fix, the original daemon remains alive after watcher/poll startup. Removing only the startup idle-clock reset makes the same test fail: it logs initial reconciliation complete, arms the activation poll, then exits idle=60s on its first housekeeping tick. Mutation restored. Successful activation re-arm also refreshes the window. Explicit shutdown and degraded-startup handling are unchanged. The candidate is not yet merged/released.

Confirmed by a real-binary regression using the existing reconcile-delay hook: startup delayed 61 seconds with --idle-min 1 and no RPC traffic. With the fix, the original daemon remains alive after watcher/poll startup. Removing only the startup idle-clock reset makes the same test fail: it logs initial reconciliation complete, arms the activation poll, then exits idle=60s on its first housekeeping tick. Mutation restored. Successful activation re-arm also refreshes the window. Explicit shutdown and degraded-startup handling are unchanged. The candidate is not yet merged/released.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
h-dv/code-index#415
No description provided.