apps
apps copied to clipboard
`Assertion Failed` error when minimumPeriod is set to 0
- I'm submitting a ...
- [x] Bug report
- [ ] Feature request
- [ ] Support request
- [ ] Other
- What is the current behavior and expected behavior? I'm currently working on upgrading a parachain to use Asynchronous Backing which requires a change in the pallet_timestamp making the MinimumPeriod = 0
impl pallet_timestamp::Config for Runtime {
....
type MinimumPeriod = ConstU64<0>;
}
This is needed because multiple parachain blocks can be built on the same relay chain block therefore they will have the same timestamp.
After applying this change every extrinsic starts failing with a message Assertion Failed
. Here's an example trying to make a simple transfer
This also happens with every other extrinsic.
Changing MinimumPeriod
to a value other than 0 fixes the problem but is not a solution since it must be set to that value for async-backing to work properly.
We also observed that this bug was also present when trying to submit an extrinsic using polkadotJs Api.
- What is the motivation for changing the behavior? With the recent upgrade to Rococo enabling async-backing more and more parachains will try to upgrade their own runtimes and encounter this very same error.
We are currently having the same issue after upgrading our Rococo Parachain to async backing with MinimumPeriod set to 0,
We used a 'poor man's approach' as a workaround to conduct some tests with a local version
Facing the same issue. Is this going to be addressed?
Facing the same issue. Is this going to be addressed?
Bandwidth is spread thin across the Repos at the moment, I will add it to the project board so it gets attention but there is quite the backlog at the moment. I'll need to do some research on this.
This seems like an issue at the API level.
This issue is resolved downstream via https://github.com/polkadot-js/api/issues/5826 and https://github.com/polkadot-js/api/pull/5829
It will added on apps either tomorrow or thursday depending on how fast I can move this weeks release cycle.
This was resolve with api update a while ago. Closing 10.12.3
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.