Skip to content
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

Merged
merged 2 commits into from
Apr 25, 2024

Conversation

alexggh
Copy link
Contributor

@alexggh alexggh commented Apr 24, 2024

... 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

... 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 <alexandru.gheorghe@parity.io>
Signed-off-by: Alexandru Gheorghe <alexandru.gheorghe@parity.io>
@alexggh alexggh added R0-silent Changes should not be mentioned in any release notes T8-polkadot This PR/Issue is related to/affects the Polkadot network. labels Apr 25, 2024
@alexggh alexggh enabled auto-merge April 25, 2024 10:10
@alexggh alexggh added this pull request to the merge queue Apr 25, 2024
Merged via the queue into master with commit 239a23d Apr 25, 2024
143 of 147 checks passed
@alexggh alexggh deleted the alexaggh/fix_cleaning_up_of_last_topology branch April 25, 2024 10:35
@hbulgarini
Copy link
Contributor

hbulgarini commented May 7, 2024

Hey @ordian @eskimor @sandreim !

Today we did the upgrade on Paseo network that upgrades the runtime to 1.2.0.
For the records: Paseo is a testnet that replicates Polkadot in every way.

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.

@ordian
Copy link
Member

ordian commented May 7, 2024

@hbulgarini this PR was not included in 1.11.0, but will be in the next release.

TarekkMA pushed a commit to moonbeam-foundation/polkadot-sdk that referenced this pull request Aug 2, 2024
…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 <alexandru.gheorghe@parity.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R0-silent Changes should not be mentioned in any release notes T8-polkadot This PR/Issue is related to/affects the Polkadot network.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Polkadot parachains not producing blocks until next session after v1.2 runtime enactement
4 participants