-
Notifications
You must be signed in to change notification settings - Fork 710
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
Instantly seal parachain block with async backing #4437
Comments
Looking into it, meanwhile can you give me some reproducing steps, what exactly are you running ? |
Yes the issue is valid, we don't have tests for this stuff. @librelois could you port your mentioned commit to polkadot-sdk? https://substrate.stackexchange.com/a/11461/73 I left here a comment on what would need to change to make it correct. |
…ng (paritytech#4442) Support async backing in `--dev` mode This PR improve the relay mock `MockValidationDataInherentDataProvider` to mach expectations of async backing runtimes. * Add para_head in the mock relay proof * Add relay slot in the mock relay proof fix paritytech#4437
After applying patch #4442, I still received a Adding this hack (https://github.com/darwinia-network/darwinia/pull/1492/files#diff-daced65c5a2c24e21e748746a2501eb6f6006d23e3d5fc15804227d84496f57aR804-R814) resolved the slot mismatch issue, but I encountered another error. Any ideas? @bkchr, I think the
|
@AurevoirXavier #4555 this should make it more obvious that you need to set |
|
…ing (paritytech#4442) Support async backing in `--dev` mode This PR improve the relay mock `MockValidationDataInherentDataProvider` to mach expectations of async backing runtimes. * Add para_head in the mock relay proof * Add relay slot in the mock relay proof fix paritytech#4437
…ing (paritytech#4442) Support async backing in `--dev` mode This PR improve the relay mock `MockValidationDataInherentDataProvider` to mach expectations of async backing runtimes. * Add para_head in the mock relay proof * Add relay slot in the mock relay proof fix paritytech#4437
…ing (paritytech#4442) Support async backing in `--dev` mode This PR improve the relay mock `MockValidationDataInherentDataProvider` to mach expectations of async backing runtimes. * Add para_head in the mock relay proof * Add relay slot in the mock relay proof fix paritytech#4437
…ing (paritytech#4442) Support async backing in `--dev` mode This PR improve the relay mock `MockValidationDataInherentDataProvider` to mach expectations of async backing runtimes. * Add para_head in the mock relay proof * Add relay slot in the mock relay proof fix paritytech#4437
…ing (paritytech#4442) Support async backing in `--dev` mode This PR improve the relay mock `MockValidationDataInherentDataProvider` to mach expectations of async backing runtimes. * Add para_head in the mock relay proof * Add relay slot in the mock relay proof fix paritytech#4437
I originally posted this question on https://substrate.stackexchange.com/questions/11457/how-to-instantly-seal-parachain-block-with-async-backing, but it seems I can't find help there.
The text was updated successfully, but these errors were encountered: