fix: support state save and restore redeploy workflow - #5375
Open
JeffreyDallas wants to merge 30 commits into
Open
fix: support state save and restore redeploy workflow#5375JeffreyDallas wants to merge 30 commits into
JeffreyDallas wants to merge 30 commits into
Conversation
|
Merging to
After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here |
Contributor
Contributor
JeffreyDallas
marked this pull request as ready for review
July 28, 2026 04:07
Contributor
Contributor
jan-milenkov
previously approved these changes
Jul 29, 2026
JeffreyDallas
marked this pull request as ready for review
August 18, 2026 14:02
jan-milenkov
requested review from
Fantomasa,
ddeskov-limechain and
jeromy-cannon
August 19, 2026 09:34
jeromy-cannon
marked this pull request as draft
August 21, 2026 12:27
- Add unit tests for PcesTrimmer covering: an unchanged file below the cutoff, a record ending exactly at the buffer boundary, a straddling file that gets truncated, multi-byte varint birth rounds, the truncateAtOffset <= 4 whole-file-delete path, an unrecognized version header, nested directories, a missing directory, and a malformed record (left untouched rather than guessed at). - wait-for-stable-saved-state.sh: fingerprint saved-state files by size+mtime instead of hashing file contents, avoiding repeated full-content I/O on every 2s poll (up to 180 times) while the node is trying to quiesce. - Remove the redundant showUser warning in getNodeStateFiles(); the thrown SoloErrors.validation.illegalArgument already carries the same message and is shown to the user. - Name the FREEZE_COMPLETE enum value in a comment next to the magic "6.0" platform_PlatformStatus check in the state-save-and-restore Taskfile. Signed-off-by: Jeffrey Tang <jeffrey@swirldslabs.com>
JeffreyDallas
marked this pull request as ready for review
August 24, 2026 21:54
Signed-off-by: JeffreyDallas <39912573+JeffreyDallas@users.noreply.github.com>
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.
Description
This pull request makes the
state-save-and-restoreworkflow safe for restoring a frozen consensus-node state into a fresh cluster with different network endpoints.It:
generate-override-network.mjs, which buildsoverride-network.jsonfrom the saved network definition and the fresh Kubernetes service endpoints, then copies it into the consensus-node podsFREEZE_COMPLETEand noInvalid State Signatureis reportedRelated Issues
Pull request (PR) checklist
package.jsonchanges have been explained to and approved by a repository managerTesting
The following manual testing was done:
examples/state-save-and-restoreworkflow on a clean kind cluster, including freeze, stable state capture, cluster recreation, endpoint override generation/copy, and restore.FREEZE_COMPLETE, both proxies became active, and noInvalid State Signaturewas reported.task verify-stateagainst the restored cluster; both nodes reported platform status6.0.git diff --check.The following was not tested: