-
Notifications
You must be signed in to change notification settings - Fork 838
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
Fix polkadot parachains not producing blocks until next session #4269
Conversation
... a few sessions too late :(, this already happened on polkadot, so as of now there are no known relay-chains without async backing enabled in runtime, but let's fix in case someone else wannts to repeat our steps. Signed-off-by: Alexandru Gheorghe <[email protected]>
Signed-off-by: Alexandru Gheorghe <[email protected]>
Hey @ordian @eskimor @sandreim ! Today we did the upgrade on Paseo network that upgrades the runtime to 1.2.0. After running the upgrade we faced the same issue as Polkadot where the parachains got stalled even if validators upgraded to the latest client release (1.11). After the epoch change, paras got back to normal. Not sure if this is still valuable or not but it seems the fix is still missing something. |
@hbulgarini this PR was not included in 1.11.0, but will be in the next release. |
…tytech#4269) ... a few sessions too late :(, this already happened on polkadot, so as of now there are no known relay-chains without async backing enabled in runtime, but let's fix it in case someone else wants to repeat our steps. Fixes: paritytech#4226 --------- Signed-off-by: Alexandru Gheorghe <[email protected]>
... a few sessions too late :(, this already happened on polkadot, so as of now there are no known relay-chains without async backing enabled in runtime, but let's fix it in case someone else wants to repeat our steps.
Fixes: #4226