-
Notifications
You must be signed in to change notification settings - Fork 514
feat(stack): replace remote runtime protocol with Effect RPC #6303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Open
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
84946a1
feat(stack): replace remote runtime protocol with Effect RPC
jgoux 46cfaa0
fix(stack): harden remote control plane
jgoux 042e1e6
fix(stack): refine control plane safeguards
jgoux 2f99a0c
fix(stack): allow long-running service shutdown
jgoux 750866d
fix(cli): preserve replacement launch state
jgoux b14618d
refactor(stack): deepen remote control client
jgoux 697db5e
refactor(stack): deepen supervisor lifecycle
jgoux fab8b98
refactor(stack): align control transport conflicts
jgoux f343951
refactor(stack): deepen supervisor replacement
jgoux 67f3e49
refactor(stack): narrow control client internals
jgoux 0b67963
docs(stack): update supervisor ownership model
jgoux 175f524
refactor(cli): narrow launch state projection
jgoux 7701c2c
fix(stack): preserve exclusion companions
jgoux 3074eec
fix(cli): classify control stop conflicts
jgoux 8838223
fix(stack): complete stable stop responses
jgoux ea45417
fix(stack): fence runtime rpc owners
jgoux 8c37a32
fix(stack): preserve control-plane startup invariants
jgoux 2639cfb
fix(cli): stabilize source build identity
jgoux 1b704e9
fix(stack): retain attached session fence
jgoux 530175d
fix(stack): close replacement lifecycle gaps
jgoux File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a supervisor crashes after leaving
stack.jsonwithlifecycle: "running",resolveManagedStackreturns that stale document and this newconnectLayercall fails withNoRunningStackErrorbecause no ready control owner can be probed. The command therefore never reachesstopDaemon, which previously acquired ownership, cleaned up the stale runtime, and allowed the stack to restart for the selected branch. Restrict the compatibility preflight to a live owner or let this specific no-owner result continue into stale-owner recovery.Useful? React with 👍 / 👎.