fix(iota-light-client): regenerate checkpoints after v1 types changes #3751
Conversation
This file contains 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
… ability to generate checkpoints in explicit way
…rate-checkpoints-after-TransactionEffectsV1-changes
…rate-checkpoints-after-TransactionEffectsV1-changes
alexsporn
approved these changes
Oct 29, 2024
miker83z
approved these changes
Oct 29, 2024
miker83z
deleted the
sc-platform/Regenerate-checkpoints-after-TransactionEffectsV1-changes
branch
6 tasks
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 of change
Due to some V1 types rename changes the checkpoint files became invalid.
This PR has been regenerating checkpoint files.
Also there is an ability to regenerate checkpoints in easy and explicit way - you have to:
cargo run --release --bin iota start --force-regenesis --with-faucetcheckpoints: []cargo run --bin generate_chk_snapshotsSee (test/README.md)
Links to any relevant issues
Fix #3665 .
Type of change
How the change has been tested
cargo test