-
Couldn't load subscription status.
- Fork 583
Fixes to migration script #15456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes to migration script #15456
Conversation
scripts/archive/migration/README.md
Outdated
|
|
||
| ``` | ||
| ./scripts/archive/migration/berkeley_migration.sh final -g ../../umt_testing/o1labs-umt-pre-fork-run-1-ledger.json -s postgres://postgres:postgres@localhost:5432/umt_testing_final -t postgres://postgres:postgres@localhost:5432/migrated -b mina_network_block_data -bs 50 -n o1labs-umt-pre-fork-run-1 -r migration-checkpoint-2381.json -fc ../../umt_testing/fork-umt-02-29-2024.json -f 3NLnD1Yp4MS9LtMXikD1YyySZNVgCXA82b5eQVpmYZ5kyTo4Xsr7 | ||
| ./scripts/archive/migration/berkeley_migration.sh final -g ../../umt_testing/o1labs-umt-pre-fork-run-1-ledger.json -s postgres://postgres:postgres@localhost:5432/umt_testing_final -t postgres://postgres:postgres@localhost:5432/migrated -b mina_network_block_data -bs 50 -n o1labs-umt-pre-fork-run-1 -r migration-checkpoint-2381.json -fc ../../umt_testing/fork-umt-02-29-2024.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| ./scripts/archive/migration/berkeley_migration.sh final -g ../../umt_testing/o1labs-umt-pre-fork-run-1-ledger.json -s postgres://postgres:postgres@localhost:5432/umt_testing_final -t postgres://postgres:postgres@localhost:5432/migrated -b mina_network_block_data -bs 50 -n o1labs-umt-pre-fork-run-1 -r migration-checkpoint-2381.json -fc ../../umt_testing/fork-umt-02-29-2024.json | |
| ./scripts/archive/migration/mina-berkeley-migration-script final -g ../../umt_testing/o1labs-umt-pre-fork-run-1-ledger.json -s postgres://postgres:postgres@localhost:5432/umt_testing_final -t postgres://postgres:postgres@localhost:5432/migrated -b mina_network_block_data -bs 50 -n o1labs-umt-pre-fork-run-1 -r migration-checkpoint-2381.json -fc ../../umt_testing/fork-umt-02-29-2024.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is part of another PR, I thought :D
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't mind merging your commit from there to here to avoid more micro PRs
|
!ci-build-me |
|
Testing the script didn't work. Going to investigate tomorrow |
|
It turned out the |
|
!approved-for-mainnet |
Problem: parameter is clearly redundant Solution: take the value from the fork config
Problem: migration verifier tool and migration script incorrectly named genesis config of the fork network as the fork config which introduced certain confusion. Solution: rename all such occurences of fork config to fork genesis config.
e0537a8 to
b228412
Compare
|
!ci-build-me |
|
!approved-for-mainnet |
|
#15467 for ensuring the docs are updated and tested as well after this |
Explain your changes:
--fork-state-hashfromfinalstepgrep '"level":"Error"'instead ofgrep Errorfor checking errors in logs--fork-configand--fork-config-fileparameters in migration script/verifier to--fork-genesis-configExplain how you tested your changes:
Checklist: