Repository navigation
Keep Tether role replacement launches under native custody - #158
Merged
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Compiled Tether role units now set
Restart=no, so a fenced or failed runtime cannot start a replacement manager invocation outside native launch custody. Native activation and boot resume retain authority over eligible replacement launches, with pending revocation completed first.The compiler-to-renderer regression covers all four Tether role kinds before and after peer revocation. It verifies the rendered restart policy and existing dependencies, while guarding Core's unchanged
Restart=alwaysdefault. The owning Tether guide documents this boundary.Static AST, Ruff and formatting checks passed. Required CI will run the existing compiler test selection and clean documentation build on this exact three-file change. Existing retained-incarnation closure checks and runtime fences are unchanged.
Refs #20.