mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-05-31 09:51:02 +00:00
Use same fmt and clippy configs as in Substrate (#7611)
* Use same rustfmt.toml as Substrate Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * format format file Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Format with new config Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Add Substrate Clippy config Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Print Clippy version in CI Otherwise its difficult to reproduce locally. Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Make fmt happy Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> * Update node/core/pvf/src/error.rs Co-authored-by: Tsvetomir Dimitrov <tsvetomir@parity.io> * Update node/core/pvf/src/error.rs Co-authored-by: Tsvetomir Dimitrov <tsvetomir@parity.io> --------- Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io> Co-authored-by: Tsvetomir Dimitrov <tsvetomir@parity.io>
This commit is contained in:
committed by
GitHub
parent
ac435c96cf
commit
342d720573
@@ -17,7 +17,8 @@
|
||||
//! This module is responsible for maintaining a consistent initialization order for all other
|
||||
//! parachains modules. It's also responsible for finalization and session change notifications.
|
||||
//!
|
||||
//! This module can throw fatal errors if session-change notifications are received after initialization.
|
||||
//! This module can throw fatal errors if session-change notifications are received after
|
||||
//! initialization.
|
||||
|
||||
use crate::{
|
||||
configuration::{self, HostConfiguration},
|
||||
@@ -128,9 +129,9 @@ pub mod pallet {
|
||||
/// Semantically a `bool`, but this guarantees it should never hit the trie,
|
||||
/// as this is cleared in `on_finalize` and Frame optimizes `None` values to be empty values.
|
||||
///
|
||||
/// As a `bool`, `set(false)` and `remove()` both lead to the next `get()` being false, but one of
|
||||
/// them writes to the trie and one does not. This confusion makes `Option<()>` more suitable for
|
||||
/// the semantics of this variable.
|
||||
/// As a `bool`, `set(false)` and `remove()` both lead to the next `get()` being false, but one
|
||||
/// of them writes to the trie and one does not. This confusion makes `Option<()>` more suitable
|
||||
/// for the semantics of this variable.
|
||||
#[pallet::storage]
|
||||
pub(super) type HasInitialized<T: Config> = StorageValue<_, ()>;
|
||||
|
||||
@@ -190,7 +191,8 @@ pub mod pallet {
|
||||
// Apply buffered session changes as the last thing. This way the runtime APIs and the
|
||||
// next block will observe the next session.
|
||||
//
|
||||
// Note that we only apply the last session as all others lasted less than a block (weirdly).
|
||||
// Note that we only apply the last session as all others lasted less than a block
|
||||
// (weirdly).
|
||||
if let Some(BufferedSessionChange { session_index, validators, queued }) =
|
||||
BufferedSessionChanges::<T>::take().pop()
|
||||
{
|
||||
|
||||
Reference in New Issue
Block a user