Teddy Ni b36c0b1189 Reap exited PID-managed app-server children (#32838) ...

## Why

An app-server child started by a previous updater can remain as a zombie after
termination. Its PID then still appears active, causing daemon shutdown to wait
until its timeout instead of removing the stale PID file.

## What changed

- Poll `waitpid` with `WNOHANG` while waiting for a PID-managed process to stop.
- Check process state before enforcing the stop deadline so an exit at the
  deadline can still be observed and cleaned up.

## Testing

Added a regression test that stops an untracked child and verifies that shutdown
finishes promptly and removes its PID file.

GitOrigin-RevId: b203cf860e4207716a6cfc36015f8ee77918d13a

2026-07-13 17:33:13 +00:00

..

backend

Reap exited PID-managed app-server children (#32838)

2026-07-13 17:33:13 +00:00

client.rs

Improve codex remote-control CLI UX (#22878)

2026-05-18 13:39:02 -07:00

lib.rs

feat(remote-control): add daemon pairing command (#29913)

2026-06-24 18:00:06 -07:00

managed_install_tests.rs

daemon: refresh updater after validated binary rollout (#21853)

2026-05-11 12:37:10 -07:00

managed_install.rs

daemon: refresh updater after validated binary rollout (#21853)

2026-05-11 12:37:10 -07:00

remote_control_client.rs

feat(remote-control): add daemon pairing command (#29913)

2026-06-24 18:00:06 -07:00

settings.rs

[daemon] Add app-server daemon lifecycle management (#20718)

2026-05-08 16:51:16 -07:00

update_loop_tests.rs

daemon: refresh updater after validated binary rollout (#21853)

2026-05-11 12:37:10 -07:00

update_loop.rs

daemon: refresh updater after validated binary rollout (#21853)

2026-05-11 12:37:10 -07:00