PRD 0034: Sidecar Restart and Shutdown Semantics #127
Reference in New Issue
Block a user
Delete Branch "prd-0034-sidecar-restart-shutdown-semantics"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #126.
Parent hotspot review: #117.
PRD:
fe6059e4a6/docs/prds/0034-sidecar-restart-shutdown-semantics.mdSummary
Implements PRD 0034 by moving SIGUSR1-triggered pipelock restarts onto the sidecar supervisor loop instead of doing restart work directly from the signal handler. Repeated restart requests coalesce by daemon name, and shutdown clears pending restarts so no daemon is respawned during teardown.
Clarifies exit-code behavior so positive child failures remain visible while signal-only shutdown returns zero instead of surfacing platform-specific negative signal codes.
Changes (3 commits)
docs(prd): add sidecar restart semanticsfix(sidecar): queue restart signalscomplete(prd): mark PRD 0034 activeRE coalescing, think that makes sense. RE clamping, think that also makes sense.
Thanks, I’ll implement those decisions in PRD 0034: repeated restart requests will coalesce by daemon name, and exit-code handling will clamp signal-only shutdown outcomes to 0 while preserving any positive child crash code.