-
Notifications
You must be signed in to change notification settings - Fork 78
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
wip: Bump polkadot to v0.9.13 #527
Conversation
NunoAlexandre
commented
Nov 26, 2021
•
edited
Loading
edited
- Bump version of polkadot
- Bump substrate
- Bump cumulus
- Fix compilation issues
- Run tests
- Update docker image
- Ensure that the relay-chain produces blocks
- Ensue that the para-chain produces blocks
I had bump it to --tag v0.9.13-rc1, which is not what cumulus points to, causing cargo to create a copy of all the substrate crates and leading to lots of error types.
As of #a62577a, running
We better wait until polkadot and substrate have finalised their respective 0.9.13 versions as going on creating forks requires forks for substrate, polkadot, and cumulus at no benefit for us right now. |
@mustermeiszer what is the best base branch for this bump? 🤔 |
Parachain. We rebase rt3-rc2 and rt4 then. Or rebase this one, when we device to not bring in polkadot-v0.9.13 in our side. Its a bit of hustle to test, if there where any migrations or other changes on the substrate side. But we will see. |
Cool, thanks man! |
This field no longer exists in frame_system::pallet::GenesisConfig.
This resolves the typing issue caused by having two versions of the same crate lingering around.
This field is no longer made available through cumulus_client_cli::RunCmd so we add it explicitly to our own Cli struct.
--chain=/chainspec.json --wasm-execution=compiled --execution=wasm | ||
--no-beefy --base-path=/data --port 30333 --rpc-port 9933 --ws-port 9944 | ||
--rpc-external --rpc-cors all --ws-external --rpc-methods=Unsafe --alice |
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.
These changes must have been caused by my editor, not intentional 🙃
Block production worked after onboarding but it halted after producing block #3.
Closed in favour of #611 |