Skip to content

fix(systemd): track user units caught mid-transition at startup - #144

Merged
b0bbywan merged 1 commit into
mainfrom
fix/systemd-transitional-startup
Sep 13, 2026
Merged

b0bbywan merged 1 commit into
mainfrom
fix/systemd-transitional-startup

Conversation

@b0bbywan

Copy link
Copy Markdown
Owner

fsnotify only sees invocation links created after the watcher starts, so a user unit snapshotted while activating (odio-screen waiting on odio-api) stayed stale. Follow those units until they settle.

Claude-Session: https://claude.ai/code/session_013gFB9WgpMajs1zcfrxyanA

fsnotify only reports invocation links, so odio-api missed user units that
settle without a new one: a unit snapshotted while activating (odio-screen
waiting on odio-api), and a restart whose start event landed while the stop
was still being watched. Follow the former, and re-read the latter.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013gFB9WgpMajs1zcfrxyanA
@b0bbywan
b0bbywan force-pushed the fix/systemd-transitional-startup branch from 66768d8 to 1a8a496 Compare September 13, 2026 13:26
@b0bbywan
b0bbywan merged commit cbca2e5 into main Sep 13, 2026
11 checks passed
@b0bbywan
b0bbywan deleted the fix/systemd-transitional-startup branch September 14, 2026 17:43
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