Skip to content

Fix macOS service start for 0.3.0 qualification - #155

Merged
elliothux merged 1 commit into
releasefrom
main
Oct 10, 2026
Merged

elliothux merged 1 commit into
releasefrom
main

Conversation

@elliothux

Copy link
Copy Markdown
Owner

macOS service start used launchctl kickstart -k after RunAtLoad bootstrap, terminating the daemon that had just started. Start now uses kickstart without termination; explicit restart retains -k. This removes a readiness/PID race observed during fresh-candidate installation qualification.

Validation: all 10 service-manager unit tests passed, including start/restart argument regression; an isolated real launchd job confirmed start preserves the running PID. Formatting and conformance source identity passed. Release notes describe the correction. Fresh release qualification is still required.

@elliothux
elliothux merged commit 78e0c60 into release Oct 10, 2026
11 checks passed

This branch was successfully deployed

2 active deployments
s3-provider-qualification — 7904d494 Deployed Oct 10, 2026 by elliothux via s3-provider-qualification #369
ai-search-qualification — 7904d494 Deployed Oct 10, 2026 by elliothux via ai-search-qualification #369
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant