kshitijk4poor 57644ec000 fix(process): a family's stop path releases its group only once the group is empty ...

Same class as the router fix: nine stop paths released their group from the owner-death supervisor
as soon as the leader exited, but members that ignore TERM or outlive the leader keep the group
alive. Releasing it let those members survive a later kill -9 of this process.

Lightpanda, real-profile Chrome, embedded cua-driver, the TTS command provider, dashboard WhatsApp
pairing, the raft and WhatsApp bridges, verify's app server, agent-browser session groups, and
Browser Use harness daemons stopped by --reload now go through release_process_group_once_empty.

New test stops a raft bridge whose TERM-ignoring helper survives. It fails when raft releases
unconditionally, and the group stays covered with the fix. Test seams moved from the per-module
release_process_groups name to the shared helper.

Reported by Greptile on #137057 (thread on the router).

2026-10-29 16:58:09 +05:30

..

__init__.py

ci: fix RUF017, RUF018, RUF022

2026-10-08 19:54:07 +02:00

environment.py

ci: ruff UP017 fixes

2026-10-09 17:34:36 +02:00

recipes.py

ci: ruff UP037 fixes

2026-10-09 17:34:38 +02:00

runner.py

fix(process): a family's stop path releases its group only once the group is empty

2026-10-29 16:58:09 +05:30