Introduce checkpoint prefix argument to migration script #15606
Merged
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
|
!ci-build-me |
|
!ci-nightly-me |
|
!ci-build-me |
SanabriaRusso
approved these changes
May 7, 2024
|
!ci-build-me |
|
!ci-nightly-me |
|
!ci-build-me |
ghost-not-in-the-shell
approved these changes
May 16, 2024
|
!approved-for-mainnet |
dkijania
deleted the
dkijania/introduce_checkpoint_prefix_to_migration_script
branch
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.
Exposing checkpoint-prefix parameter in berkeley migration script. It might be helpful when we have more that one migration on single machine (devnet and mainnet) and for some reason we would like to keep both checkpoints. This is the case for our cron job which is used for more than one network and it need to be aware of checkpoint prefixes