Do not use rely on the block initialization when calling runtime APIs (#2123)

* Don't initialize block when calling runtime APIs

* Adapt check_validation_outputs

We split the code path for the inclusion and for the commitments checking.

* Slap #[skip_initialize_block] on safe runtime APIs

That is, those that should not be affected by this attribute

* Make `Scheduled` not ephemeral

So that it is persisted in the storage and ready to be inspected
by the runtime APIs. This is in contrast to what was before, where we
would remove the storage entry and then rely on the scheduling performed
by `on_initialize` again.

* Add a big fat comment

* Typos

Co-authored-by: Robert Habermeier <rphmeier@gmail.com>

* Move session change to the end of the current block

Previously, it was the beginning of the next block. This allows us to
put #[skip_initialize_block]

* Update tests

* Fix a test in paras registrar

Also refactor it a bit so the next time there are more chances this kind
of issue is diagnosed quicker.

* Add for_runtime_api to inclusion's check_validation_outputs

Co-authored-by: Robert Habermeier <rphmeier@gmail.com>
This commit is contained in:
Sergei Shulepov
2020-12-22 00:02:22 +01:00
committed by GitHub
parent 01d271caeb
commit 4405f52e2d
8 changed files with 114 additions and 77 deletions
+5 -5
View File
@@ -17,19 +17,19 @@
//! Utilities that don't belong to any particular module but may draw
//! on all modules.
use sp_runtime::traits::{One, Saturating};
use sp_runtime::traits::Saturating;
use primitives::v1::{Id as ParaId, PersistedValidationData, TransientValidationData};
use crate::{configuration, paras, dmp, hrmp};
/// Make the persisted validation data for a particular parachain.
/// Make the persisted validation data for a particular parachain and a specified relay-parent.
///
/// This ties together the storage of several modules.
pub fn make_persisted_validation_data<T: paras::Config + hrmp::Config>(
para_id: ParaId,
relay_parent_number: T::BlockNumber,
) -> Option<PersistedValidationData<T::BlockNumber>> {
let config = <configuration::Module<T>>::config();
let relay_parent_number = <frame_system::Module<T>>::block_number() - One::one();
Some(PersistedValidationData {
parent_head: <paras::Module<T>>::para_head(&para_id)?,
@@ -40,14 +40,14 @@ pub fn make_persisted_validation_data<T: paras::Config + hrmp::Config>(
})
}
/// Make the transient validation data for a particular parachain.
/// Make the transient validation data for a particular parachain and a specified relay-parent.
///
/// This ties together the storage of several modules.
pub fn make_transient_validation_data<T: paras::Config + dmp::Config>(
para_id: ParaId,
relay_parent_number: T::BlockNumber,
) -> Option<TransientValidationData<T::BlockNumber>> {
let config = <configuration::Module<T>>::config();
let relay_parent_number = <frame_system::Module<T>>::block_number() - One::one();
let freq = config.validation_upgrade_frequency;
let delay = config.validation_upgrade_delay;