Local sealing #6966
Merged
Local sealing #6966
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
|
This currently has a test for when a single node is chosen to recover. (infra.network.recover) |
eddyashton
reviewed
Apr 10, 2025
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
achamayou
reviewed
May 14, 2025
achamayou
reviewed
May 15, 2025
achamayou
reviewed
May 15, 2025
achamayou
reviewed
May 15, 2025
cjen1-msft
commented
May 16, 2025
cjen1-msft
commented
May 16, 2025
cjen1-msft
commented
May 16, 2025
cjen1-msft
commented
May 16, 2025
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.
Add local sealing flow, to skip waiting for recovery shares when there is a previous sealed ledger secret.
This simply omits the
submit_recovery_sharesrpc, and still requires thetransition_to_openproposal.