Skip to content

Register the LatchStream service when setup moves an older engine (4.1.1) - #24

Merged
MrBeldum merged 1 commit into
mainfrom
fix/legacy-engine-service
Oct 2, 2026
Merged

MrBeldum merged 1 commit into
mainfrom
fix/legacy-engine-service

Conversation

@MrBeldum

@MrBeldum MrBeldum commented Oct 2, 2026

Copy link
Copy Markdown
Owner

Found while preparing to migrate the Windows PC: setup decided whether to run the engine step from whether an engine was running. An engine in the old C:\Program Files\BroLink\engine folder is running, so the step was skipped, after the retire step had already moved the folder and deleted BroLinkStream. Nothing registered LatchStream, so the engine would have run only once someone signed in. An engine in the old folder now counts as needing the step (streamer::in_old_folder), in both places that build the plan.

Version 4.1.1.

🤖 Generated with Claude Code

Setup builds its plan from whether an engine is up, and an engine in the
folder 4.0 used is up, so the plan skipped the engine step. The retire step
had by then moved the folder and deleted BroLinkStream, and nothing
registered LatchStream: the engine would have run only once someone signed
in. An engine in the old folder now counts as needing the step.

Version 4.1.1.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@MrBeldum
MrBeldum merged commit 291cc9e into main Oct 2, 2026
5 checks passed
@MrBeldum
MrBeldum deleted the fix/legacy-engine-service branch October 2, 2026 17:14
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