orchestrator-sm: carry recovery attempt on RecoverComponent - #407
Draft
rusty1968 wants to merge 1 commit into
Draft
orchestrator-sm: carry recovery attempt on RecoverComponent#407rusty1968 wants to merge 1 commit into
rusty1968 wants to merge 1 commit into
Conversation
Emit the per-component retry count as RecoverComponent { id, attempt } so
the driver picks a recovery source per attempt without its own counter.
rusty1968
force-pushed
the
sm-recover-attempt
branch
from
August 7, 2026 23:08
ba45811 to
e69afa8
Compare
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
1 participant
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.
Effect::RecoverComponentnow carries{ id, attempt }instead of justid.attemptis the component's consecutive-recovery count (0 on the first try), taken straight from the core's retry counter.Passing it in-band lets the Platform driver pick a recovery source per attempt (e.g. slot A → slot B → golden) without keeping its own counter, which could drift from the core's since the driver never sees when a recovery succeeds.
No behavior change in the core: the retry cap is still measured against the same counter;
attemptonly rides out on the effect. Tests updated.