2 Commits

Include renames

Author	SHA1	Message	Date
stroblmeandClaude Opus 5	f5ea960e24	Let a connector's teardown cancellation through too ... ConnectorNode.stop cancelled its poll task and then caught CancelledError around the await — the fourth site of the trap 93e4527 closed elsewhere, swallowing a cancellation aimed at whoever asked for the teardown. It now calls the shared Node._cancel_task, which keeps retrieving whatever the loop raised on its way out, as the old `except (CancelledError, Exception)` did. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K1moruzue2kTJd3uVisgNk	2026-08-28 11:56:19 +02:00
stroblme	93e45274d0	Let a teardown's cancellation through, and reap the workers it leaves ... Node stop paths cancelled their background task and then caught CancelledError around the await, which swallows a cancellation aimed at the caller — the trap Supervisor._cancel already documents. One shared Node._cancel_task now waits the way the supervisor does; mqtt's publisher and subscription and delay's cron call it. The api container also collected zombie python workers: orphaned when --reload replaces the process holding their handle, they reparent onto a PID 1 that reaps nothing but its own. `init: true` on the backend service.	2026-08-28 11:27:01 +02:00