You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Independent CLI/daemon ownership with missing or stale daemon.addr #146
Awareness tracker for the independent-process portion of #136, separated from the daemon-local fix merged in #139 at the maintainer's request. Original fork tracker: Seagulls#21.
#139 protects topology changes within one daemon against admitted readers/writers and queued work. It does not establish ownership between independent CLI and desktop/daemon processes sharing one native home.
A separate CLI process must not infer that offline root mutation is safe solely because daemon.addr is missing, stale or unreachable. The related lifecycle requirement is that the desktop can start when the Steam Deck Game Mode plugin already runs opensave-cli daemon.
Context and considerations
The presence lock originally proposed in #139 blocked desktop startup beside the CLI daemon. The maintainer requested removing it and considering graceful takeover separately: #139 (comment).
Considerations for a maintainer-designed follow-up:
Coordinate independent root edits with native-home ownership, including missing/stale/unreachable daemon.addr.
Preserve legitimate offline CLI editing when no daemon owns the home.
If takeover is used, drain active work safely and handle timeout/failure without assuming ownership is free.
Document mixed-version limits.
Validate with real independent CLI/daemon processes, disposable homes/SQLite and synthetic save files.
Evidence and scope
The existing #136 regression demonstrates the original daemon-local race; it is not an independent two-process reproduction of this remaining scenario. This report records the outstanding contract and known startup conflict without claiming new reproduction results or deployed save loss.
Filed for awareness and maintainer-led design, prioritisation and implementation. No implementation commitment, prescribed solution or release milestone is proposed here.
Activity