-
Notifications
You must be signed in to change notification settings - Fork 709
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
Introduce BlockWeightsForAsyncBacking
and MAXIMUM_BLOCK_WEIGHT_FOR_ASYNC_BACKING
to bridges primitives
#2966
Conversation
…_ASYNC_BACKING` to bridges primitives
/// We allow for 2 seconds of compute with a 6 second average block. | ||
/// | ||
/// This is a copy-paste of system parachain runtimes switched to async backing (https://github.com/paritytech/polkadot-sdk/pull/2949). | ||
const MAXIMUM_BLOCK_WEIGHT_FOR_ASYNC_BACKING: Weight = Weight::from_parts( |
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 makes no sense? Either the runtime is running using async backing or not. This means you should update BlockWeights
directly.
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.
Runtime's BlockWeights
are updated directly in that #2949.
Here we try to keep bridges primitives in sync.
Bridges repo is partially migrated to the polkadot-sdk
, the relayer part is missing, and we use these primitives for relayer code also (I will double-check if it is really needed now), that's the reason we have these "duplicite" copies. From time to time, we sync/backport bridges repo with polkadot-sdk.
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.
Hmm okay.
42f5d1b
into
mrcnski/enable-async-backing-on-testnet-system-chains
Fixes: https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/4943591