mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-04-26 20:27:58 +00:00
9a31b2c341
* Add a new host function for reporting fatal errors * Fix one of the wasmtime executor tests * Have `#[runtime_interface(wasm_only)]` actually mean WASM-only, and not no_std-only * Print out errors through `Display` instead of `Debug` * Switch one more trait to require `Error` for its error instead of only `Debug` * Align to review comments
817 lines
30 KiB
Rust
817 lines
30 KiB
Rust
// This file is part of Substrate.
|
|
|
|
// Copyright (C) 2021-2022 Parity Technologies (UK) Ltd.
|
|
// SPDX-License-Identifier: Apache-2.0
|
|
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
// you may not use this file except in compliance with the License.
|
|
// You may obtain a copy of the License at
|
|
//
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
//
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
// See the License for the specific language governing permissions and
|
|
// limitations under the License.
|
|
|
|
//! # Try-runtime
|
|
//!
|
|
//! Substrate's ultimate testing framework for the power users.
|
|
//!
|
|
//! > As the name suggests, `try-runtime` is a detailed testing framework that gives you a lot of
|
|
//! control over what is being executed in which environment. It is recommended that user's first
|
|
//! familiarize themselves with substrate in depth, particularly the execution model. It is critical
|
|
//! to deeply understand how the wasm/native interactions, and the runtime apis work in the
|
|
//! substrate runtime, before commencing to working with `try-runtime`.
|
|
//!
|
|
//! #### Resources
|
|
//!
|
|
//! Some resources about the above:
|
|
//!
|
|
//! 1. <https://docs.substrate.io/v3/tools/try-runtime>
|
|
//! 2. <https://www.crowdcast.io/e/substrate-seminar/41>
|
|
//! 3. <https://docs.substrate.io/v3/advanced/executor>
|
|
//!
|
|
//! ---
|
|
//!
|
|
//! ## Overview
|
|
//!
|
|
//! The basis of all try-runtime commands is the same: connect to a live node, scrape its *state*
|
|
//! and put it inside a `TestExternalities`, then call into a *specific runtime-api* using the given
|
|
//! state and some *runtime*.
|
|
//!
|
|
//! All of the variables in the above statement are made *italic*. Let's look at each of them:
|
|
//!
|
|
//! 1. **State** is the key-value pairs of data that comprise the canonical information that any
|
|
//! blockchain is keeping. A state can be full (all key-value pairs), or be partial (only pairs
|
|
//! related to some pallets). Moreover, some keys are special and are not related to specific
|
|
//! pallets, known as [`well_known_keys`] in substrate. The most important of these is the
|
|
//! `:CODE:` key, which contains the code used for execution, when wasm execution is chosen.
|
|
//!
|
|
//! 2. *A runtime-api* call is a call into a function defined in the runtime, *on top of a given
|
|
//! state*. Each subcommand of `try-runtime` utilizes a specific *runtime-api*.
|
|
//!
|
|
//! 3. Finally, the **runtime** is the actual code that is used to execute the aforementioned
|
|
//! runtime-api. All substrate based chains always have two runtimes: native and wasm. The
|
|
//! decision of which one is chosen is non-trivial. First, let's look at the options:
|
|
//!
|
|
//! 1. Native: this means that the runtime that is **in your codebase**, aka whatever you see in
|
|
//! your editor, is being used. This runtime is easier for diagnostics. We refer to this as
|
|
//! the "local runtime".
|
|
//!
|
|
//! 2. Wasm: this means that whatever is stored in the `:CODE:` key of the state that your
|
|
//! scrape is being used. In plain sight, since the entire state (including `:CODE:`) is
|
|
//! scraped from a remote chain, you could conclude that the wasm runtime, if used, is always
|
|
//! equal to the canonical runtime of the live chain (i.e. NOT the "local runtime"). That's
|
|
//! factually true, but then the testing would be quite lame. Typically, with try-runtime,
|
|
//! you don't want to execute whatever code is already on the live chain. Instead, you want
|
|
//! your local runtime (which typically includes a non-released feature) to be used. This is
|
|
//! why try-runtime overwrites the wasm runtime (at `:CODE:`) with the local runtime as well.
|
|
//! That being said, this behavior can be controlled in certain subcommands with a special
|
|
//! flag (`--overwrite-wasm-code`).
|
|
//!
|
|
//! The decision of which runtime is eventually used is based on two facts:
|
|
//!
|
|
//! 1. `--execution` flag. If you specify `wasm`, then it is *always* wasm. If it is `native`, then
|
|
//! if and ONLY IF the spec versions match, then the native runtime is used. Else, wasm runtime
|
|
//! is used again.
|
|
//! 2. `--chain` flag (if present in your cli), which determines *which local runtime*, is selected.
|
|
//! This will specify:
|
|
//! 1. which native runtime is used, if you select `--execution Native`
|
|
//! 2. which wasm runtime is used to replace the `:CODE:`, if try-runtime is instructed to do
|
|
//! so.
|
|
//!
|
|
//! All in all, if the term "local runtime" is used in the rest of this crate's documentation, it
|
|
//! means either the native runtime, or the wasm runtime when overwritten inside `:CODE:`. In other
|
|
//! words, it means your... well, "local runtime", regardless of wasm or native.
|
|
//!
|
|
//! //! See [`Command`] for more information about each command's specific customization flags, and
|
|
//! assumptions regarding the runtime being used.
|
|
//!
|
|
//! Finally, To make sure there are no errors regarding this, always run any `try-runtime` command
|
|
//! with `executor=trace` logging targets, which will specify which runtime is being used per api
|
|
//! call.
|
|
//!
|
|
//! Furthermore, other relevant log targets are: `try-runtime::cli`, `remote-ext`, and `runtime`.
|
|
//!
|
|
//! ## Spec name check
|
|
//!
|
|
//! A common pitfall is that you might be running some test on top of the state of chain `x`, with
|
|
//! the runtime of chain `y`. To avoid this all commands do a spec-name check before executing
|
|
//! anything by default. This will check the spec name of the remote node your are connected to,
|
|
//! with the spec name of your local runtime and ensure that they match.
|
|
//!
|
|
//! Should you need to disable this on certain occasions, a top level flag of `--no-spec-name-check`
|
|
//! can be used.
|
|
//!
|
|
//! The spec version is also always inspected, but if it is a mismatch, it will only emit a warning.
|
|
//!
|
|
//! ## Note nodes that operate with `try-runtime`
|
|
//!
|
|
//! There are a number of flags that need to be preferably set on a running node in order to work
|
|
//! well with try-runtime's expensive RPC queries:
|
|
//!
|
|
//! - set `--rpc-max-payload 1000` to ensure large RPC queries can work.
|
|
//! - set `--ws-max-out-buffer-capacity 1000` to ensure the websocket connection can handle large
|
|
//! RPC queries.
|
|
//! - set `--rpc-cors all` to ensure ws connections can come through.
|
|
//!
|
|
//! Note that *none* of the try-runtime operations need unsafe RPCs.
|
|
//!
|
|
//! ## Migration Best Practices
|
|
//!
|
|
//! One of the main use-cases of try-runtime is using it for testing storage migrations. The
|
|
//! following points makes sure you can *effectively* test your migrations with try-runtime.
|
|
//!
|
|
//! #### Adding pre/post hooks
|
|
//!
|
|
//! One of the gems that come only in the `try-runtime` feature flag is the `pre_upgrade` and
|
|
//! `post_upgrade` hooks for `OnRuntimeUpgrade`. This trait is implemented either inside the
|
|
//! pallet, or manually in a runtime, to define a migration. In both cases, these functions can be
|
|
//! added, given the right flag:
|
|
//!
|
|
//! ```ignore
|
|
//! #[cfg(feature = try-runtime)]
|
|
//! fn pre_upgrade() -> Result<(), &'static str> {}
|
|
//!
|
|
//! #[cfg(feature = try-runtime)]
|
|
//! fn post_upgrade() -> Result<(), &'static str> {}
|
|
//! ```
|
|
//!
|
|
//! (The pallet macro syntax will support this simply as a part of `#[pallet::hooks]`).
|
|
//!
|
|
//! These hooks allow you to execute some code, only within the `on-runtime-upgrade` command, before
|
|
//! and after the migration. If any data needs to be temporarily stored between the pre/post
|
|
//! migration hooks, `OnRuntimeUpgradeHelpersExt` can help with that. Note that you should be
|
|
//! mindful with any mutable storage ops in the pre/post migration checks, as you almost certainly
|
|
//! will not want to mutate any of the storage that is to be migrated.
|
|
//!
|
|
//! #### Logging
|
|
//!
|
|
//! It is super helpful to make sure your migration code uses logging (always with a `runtime` log
|
|
//! target prefix, e.g. `runtime::balance`) and state exactly at which stage it is, and what it is
|
|
//! doing.
|
|
//!
|
|
//! #### Guarding migrations
|
|
//!
|
|
//! Always make sure that any migration code is guarded either by `StorageVersion`, or by some
|
|
//! custom storage item, so that it is NEVER executed twice, even if the code lives in two
|
|
//! consecutive runtimes.
|
|
//!
|
|
//! ## Examples
|
|
//!
|
|
//! Run the migrations of the local runtime on the state of polkadot, from the polkadot repo where
|
|
//! we have `--chain polkadot-dev`, on the latest finalized block's state
|
|
//!
|
|
//! ```sh
|
|
//! RUST_LOG=runtime=trace,try-runtime::cli=trace,executor=trace \
|
|
//! cargo run try-runtime \
|
|
//! --execution Native \
|
|
//! --chain polkadot-dev \
|
|
//! on-runtime-upgrade \
|
|
//! live \
|
|
//! --uri wss://rpc.polkadot.io
|
|
//! # note that we don't pass any --at, nothing means latest block.
|
|
//! ```
|
|
//!
|
|
//! Same as previous one, but let's say we want to run this command from the substrate repo, where
|
|
//! we don't have a matching spec name/version.
|
|
//!
|
|
//! ```sh
|
|
//! RUST_LOG=runtime=trace,try-runtime::cli=trace,executor=trace \
|
|
//! cargo run try-runtime \
|
|
//! --execution Native \
|
|
//! --chain dev \
|
|
//! --no-spec-name-check \ # mind this one!
|
|
//! on-runtime-upgrade \
|
|
//! live \
|
|
//! --uri wss://rpc.polkadot.io
|
|
//! ```
|
|
//!
|
|
//! Same as the previous one, but run it at specific block number's state. This means that this
|
|
//! block hash's state shall not yet have been pruned in `rpc.polkadot.io`.
|
|
//!
|
|
//! ```sh
|
|
//! RUST_LOG=runtime=trace,try-runtime::cli=trace,executor=trace \
|
|
//! cargo run try-runtime \
|
|
//! --execution Native \
|
|
//! --chain dev \
|
|
//! --no-spec-name-check \ # mind this one! on-runtime-upgrade \
|
|
//! on-runtime-upgrade \
|
|
//! live \
|
|
//! --uri wss://rpc.polkadot.io \
|
|
//! --at <block-hash>
|
|
//! ```
|
|
//!
|
|
//! Moving to `execute-block` and `offchain-workers`. For these commands, you always needs to
|
|
//! specify a block hash. For the rest of these examples, we assume we're in the polkadot repo.
|
|
//!
|
|
//! First, let's assume you are in a branch that has the same spec name/version as the live polkadot
|
|
//! network.
|
|
//!
|
|
//! ```sh
|
|
//! RUST_LOG=runtime=trace,try-runtime::cli=trace,executor=trace \
|
|
//! cargo run try-runtime \
|
|
//! --execution Wasm \
|
|
//! --chain polkadot-dev \
|
|
//! --uri wss://rpc.polkadot.io \
|
|
//! execute-block \
|
|
//! live \
|
|
//! --at <block-hash>
|
|
//! ```
|
|
//!
|
|
//! This is wasm, so it will technically execute the code that lives on the live network. Let's say
|
|
//! you want to execute your local runtime. Since you have a matching spec versions, you can simply
|
|
//! change `--execution Wasm` to `--execution Native` to achieve this. Your logs of `executor=trace`
|
|
//! should show something among the lines of:
|
|
//!
|
|
//! ```text
|
|
//! Request for native execution succeeded (native: polkadot-9900 (parity-polkadot-0.tx7.au0), chain: polkadot-9900 (parity-polkadot-0.tx7.au0))
|
|
//! ```
|
|
//!
|
|
//! If you don't have matching spec versions, then are doomed to execute wasm. In this case, you can
|
|
//! manually overwrite the wasm code with your local runtime:
|
|
//!
|
|
//! ```sh
|
|
//! RUST_LOG=runtime=trace,try-runtime::cli=trace,executor=trace \
|
|
//! cargo run try-runtime \
|
|
//! --execution Wasm \
|
|
//! --chain polkadot-dev \
|
|
//! execute-block \
|
|
//! live \
|
|
//! --uri wss://rpc.polkadot.io \
|
|
//! --at <block-hash> \
|
|
//! --overwrite-wasm-code
|
|
//! ```
|
|
//!
|
|
//! For all of these blocks, the block with hash `<block-hash>` is being used, and the initial state
|
|
//! is the state of the parent hash. This is because by omitting `ExecuteBlockCmd::block_at`, the
|
|
//! `--at` is used for both. This should be good enough for 99% of the cases. The only case where
|
|
//! you need to specify `block-at` and `block-ws-uri` is with snapshots. Let's say you have a file
|
|
//! `snap` and you know it corresponds to the state of the parent block of `X`. Then you'd do:
|
|
//!
|
|
//! ```sh
|
|
//! RUST_LOG=runtime=trace,try-runtime::cli=trace,executor=trace \
|
|
//! cargo run try-runtime \
|
|
//! --execution Wasm \
|
|
//! --chain polkadot-dev \
|
|
//! --uri wss://rpc.polkadot.io \
|
|
//! execute-block \
|
|
//! --block-at <x> \
|
|
//! --block-ws-uri wss://rpc.polkadot.io \
|
|
//! --overwrite-wasm-code \
|
|
//! snap \
|
|
//! -s snap \
|
|
//! ```
|
|
|
|
use parity_scale_codec::Decode;
|
|
use remote_externalities::{
|
|
Builder, Mode, OfflineConfig, OnlineConfig, SnapshotConfig, TestExternalities,
|
|
};
|
|
use sc_chain_spec::ChainSpec;
|
|
use sc_cli::{CliConfiguration, ExecutionStrategy, WasmExecutionMethod};
|
|
use sc_executor::NativeElseWasmExecutor;
|
|
use sc_service::{Configuration, NativeExecutionDispatch};
|
|
use sp_core::{
|
|
offchain::{
|
|
testing::{TestOffchainExt, TestTransactionPoolExt},
|
|
OffchainDbExt, OffchainWorkerExt, TransactionPoolExt,
|
|
},
|
|
storage::{well_known_keys, StorageData, StorageKey},
|
|
testing::TaskExecutor,
|
|
traits::TaskExecutorExt,
|
|
twox_128, H256,
|
|
};
|
|
use sp_externalities::Extensions;
|
|
use sp_keystore::{testing::KeyStore, KeystoreExt};
|
|
use sp_runtime::{
|
|
traits::{Block as BlockT, NumberFor},
|
|
DeserializeOwned,
|
|
};
|
|
use sp_state_machine::{InMemoryProvingBackend, OverlayedChanges, StateMachine};
|
|
use std::{fmt::Debug, path::PathBuf, str::FromStr};
|
|
|
|
mod commands;
|
|
pub(crate) mod parse;
|
|
pub(crate) const LOG_TARGET: &'static str = "try-runtime::cli";
|
|
|
|
/// Possible commands of `try-runtime`.
|
|
#[derive(Debug, Clone, clap::Subcommand)]
|
|
pub enum Command {
|
|
/// Execute the migrations of the "local runtime".
|
|
///
|
|
/// This uses a custom runtime api call, namely "TryRuntime_on_runtime_upgrade".
|
|
///
|
|
/// This always overwrites the wasm code with the local runtime (specified by `--chain`), to
|
|
/// ensure the new migrations are being executed. Re-executing already existing migrations is
|
|
/// evidently not very exciting.
|
|
OnRuntimeUpgrade(commands::on_runtime_upgrade::OnRuntimeUpgradeCmd),
|
|
|
|
/// Executes the given block against some state.
|
|
///
|
|
/// Unlike [`Command::OnRuntimeUpgrade`], this command needs two inputs: the state, and the
|
|
/// block data. Since the state could be cached (see [`State::Snap`]), different flags are
|
|
/// provided for both. `--block-at` and `--block-uri`, if provided, are only used for fetching
|
|
/// the block. For convenience, these flags can be both emitted, if the [`State::Live`] is
|
|
/// being used.
|
|
///
|
|
/// Note that by default, this command does not overwrite the code, so in wasm execution, the
|
|
/// live chain's code is used. This can be disabled if desired, see
|
|
/// `ExecuteBlockCmd::overwrite_wasm_code`.
|
|
///
|
|
/// Note that if you do overwrite the wasm code, or generally use the local runtime for this,
|
|
/// you might
|
|
/// - not be able to decode the block, if the block format has changed.
|
|
/// - quite possibly will get a signature verification failure, since the spec and
|
|
/// transaction version are part of the signature's payload, and if they differ between
|
|
/// your local runtime and the remote counterparts, the signatures cannot be verified.
|
|
/// - almost certainly will get a state root mismatch, since, well, you are executing a
|
|
/// different state transition function.
|
|
///
|
|
/// To make testing slightly more dynamic, you can disable the state root check by enabling
|
|
/// `ExecuteBlockCmd::no_check`. If you get signature verification errors, you should
|
|
/// manually tweak your local runtime's spec version to fix this.
|
|
///
|
|
/// A subtle detail of execute block is that if you want to execute block 100 of a live chain
|
|
/// again, you need to scrape the state of block 99. This is already done automatically if you
|
|
/// use [`State::Live`], and the parent hash of the target block is used to scrape the state.
|
|
/// If [`State::Snap`] is being used, then this needs to be manually taken into consideration.
|
|
///
|
|
/// This executes the same runtime api as normal block import, namely `Core_execute_block`. If
|
|
/// `ExecuteBlockCmd::no_check` is set, it uses a custom, try-runtime-only runtime
|
|
/// api called `TryRuntime_execute_block_no_check`.
|
|
ExecuteBlock(commands::execute_block::ExecuteBlockCmd),
|
|
|
|
/// Executes *the offchain worker hooks* of a given block against some state.
|
|
///
|
|
/// Similar to [`Command::ExecuteBlock`], this command needs two inputs: the state, and the
|
|
/// header data. Likewise, `--header-at` and `--header-uri` can be filled, or omitted if
|
|
/// [`State::Live`] is used.
|
|
///
|
|
/// Similar to [`Command::ExecuteBlock`], this command does not overwrite the code, so in wasm
|
|
/// execution, the live chain's code is used. This can be disabled if desired, see
|
|
/// `OffchainWorkerCmd::overwrite_wasm_code`.
|
|
///
|
|
/// This executes the same runtime api as normal block import, namely
|
|
/// `OffchainWorkerApi_offchain_worker`.
|
|
OffchainWorker(commands::offchain_worker::OffchainWorkerCmd),
|
|
|
|
/// Follow the given chain's finalized blocks and apply all of its extrinsics.
|
|
///
|
|
/// This is essentially repeated calls to [`Command::ExecuteBlock`], whilst the local runtime
|
|
/// is always at use, the state root check is disabled, and the state is persisted between
|
|
/// executions.
|
|
///
|
|
/// This allows the behavior of a new runtime to be inspected over a long period of time, with
|
|
/// realistic transactions coming as input.
|
|
///
|
|
/// NOTE: this does NOT execute the offchain worker hooks of mirrored blocks. This might be
|
|
/// added in the future.
|
|
///
|
|
/// This does not support snapshot states, and can only work with a remote chain. Upon first
|
|
/// connections, starts listening for finalized block events. Upon first block notification, it
|
|
/// initializes the state from the remote node, and starts applying that block, plus all the
|
|
/// blocks that follow, to the same growing state.
|
|
FollowChain(commands::follow_chain::FollowChainCmd),
|
|
}
|
|
|
|
/// Shared parameters of the `try-runtime` commands
|
|
#[derive(Debug, Clone, clap::Parser)]
|
|
pub struct SharedParams {
|
|
/// Shared parameters of substrate cli.
|
|
#[allow(missing_docs)]
|
|
#[clap(flatten)]
|
|
pub shared_params: sc_cli::SharedParams,
|
|
|
|
/// The execution strategy that should be used.
|
|
#[clap(long, value_name = "STRATEGY", arg_enum, ignore_case = true, default_value = "Wasm")]
|
|
pub execution: ExecutionStrategy,
|
|
|
|
/// Type of wasm execution used.
|
|
#[clap(
|
|
long = "wasm-execution",
|
|
value_name = "METHOD",
|
|
possible_values = WasmExecutionMethod::variants(),
|
|
ignore_case = true,
|
|
default_value = "Compiled"
|
|
)]
|
|
pub wasm_method: WasmExecutionMethod,
|
|
|
|
/// The number of 64KB pages to allocate for Wasm execution. Defaults to
|
|
/// [`sc_service::Configuration.default_heap_pages`].
|
|
#[clap(long)]
|
|
pub heap_pages: Option<u64>,
|
|
|
|
/// When enabled, the spec name check will not panic, and instead only show a warning.
|
|
#[clap(long)]
|
|
pub no_spec_name_check: bool,
|
|
}
|
|
|
|
/// Our `try-runtime` command.
|
|
///
|
|
/// See [`Command`] for more info.
|
|
#[derive(Debug, Clone, clap::Parser)]
|
|
pub struct TryRuntimeCmd {
|
|
#[clap(flatten)]
|
|
pub shared: SharedParams,
|
|
|
|
#[clap(subcommand)]
|
|
pub command: Command,
|
|
}
|
|
|
|
/// The source of runtime *state* to use.
|
|
#[derive(Debug, Clone, clap::Subcommand)]
|
|
pub enum State {
|
|
/// Use a state snapshot as the source of runtime state.
|
|
///
|
|
/// This can be crated by passing a value to [`State::Live::snapshot_path`].
|
|
Snap {
|
|
#[clap(short, long)]
|
|
snapshot_path: PathBuf,
|
|
},
|
|
|
|
/// Use a live chain as the source of runtime state.
|
|
Live {
|
|
/// The url to connect to.
|
|
#[clap(
|
|
short,
|
|
long,
|
|
parse(try_from_str = parse::url),
|
|
)]
|
|
uri: String,
|
|
|
|
/// The block hash at which to fetch the state.
|
|
///
|
|
/// If non provided, then the latest finalized head is used. This is particularly useful
|
|
/// for [`Command::OnRuntimeUpgrade`].
|
|
#[clap(
|
|
short,
|
|
long,
|
|
multiple_values = false,
|
|
parse(try_from_str = parse::hash),
|
|
)]
|
|
at: Option<String>,
|
|
|
|
/// An optional state snapshot file to WRITE to. Not written if set to `None`.
|
|
#[clap(short, long)]
|
|
snapshot_path: Option<PathBuf>,
|
|
|
|
/// The pallets to scrape. If empty, entire chain state will be scraped.
|
|
#[clap(short, long, require_delimiter = true)]
|
|
pallets: Option<Vec<String>>,
|
|
|
|
/// Fetch the child-keys as well.
|
|
///
|
|
/// Default is `false`, if specific `pallets` are specified, true otherwise. In other
|
|
/// words, if you scrape the whole state the child tree data is included out of the box.
|
|
/// Otherwise, it must be enabled explicitly using this flag.
|
|
#[clap(long, require_delimiter = true)]
|
|
child_tree: bool,
|
|
},
|
|
}
|
|
|
|
impl State {
|
|
/// Create the [`remote_externalities::Builder`] from self.
|
|
pub(crate) fn builder<Block: BlockT + DeserializeOwned>(&self) -> sc_cli::Result<Builder<Block>>
|
|
where
|
|
Block::Hash: FromStr,
|
|
<Block::Hash as FromStr>::Err: Debug,
|
|
{
|
|
Ok(match self {
|
|
State::Snap { snapshot_path } =>
|
|
Builder::<Block>::new().mode(Mode::Offline(OfflineConfig {
|
|
state_snapshot: SnapshotConfig::new(snapshot_path),
|
|
})),
|
|
State::Live { snapshot_path, pallets, uri, at, child_tree } => {
|
|
let at = match at {
|
|
Some(at_str) => Some(hash_of::<Block>(at_str)?),
|
|
None => None,
|
|
};
|
|
let mut builder = Builder::<Block>::new()
|
|
.mode(Mode::Online(OnlineConfig {
|
|
transport: uri.to_owned().into(),
|
|
state_snapshot: snapshot_path.as_ref().map(SnapshotConfig::new),
|
|
pallets: pallets.clone().unwrap_or_default(),
|
|
at,
|
|
}))
|
|
.inject_hashed_key(
|
|
&[twox_128(b"System"), twox_128(b"LastRuntimeUpgrade")].concat(),
|
|
);
|
|
if *child_tree {
|
|
builder = builder.inject_default_child_tree_prefix();
|
|
}
|
|
builder
|
|
},
|
|
})
|
|
}
|
|
|
|
/// Get the uri, if self is `Live`.
|
|
pub(crate) fn live_uri(&self) -> Option<String> {
|
|
match self {
|
|
State::Live { uri, .. } => Some(uri.clone()),
|
|
_ => None,
|
|
}
|
|
}
|
|
}
|
|
|
|
impl TryRuntimeCmd {
|
|
pub async fn run<Block, ExecDispatch>(&self, config: Configuration) -> sc_cli::Result<()>
|
|
where
|
|
Block: BlockT<Hash = H256> + serde::de::DeserializeOwned,
|
|
Block::Header: serde::de::DeserializeOwned,
|
|
Block::Hash: FromStr,
|
|
<Block::Hash as FromStr>::Err: Debug,
|
|
NumberFor<Block>: FromStr,
|
|
<NumberFor<Block> as FromStr>::Err: Debug,
|
|
ExecDispatch: NativeExecutionDispatch + 'static,
|
|
{
|
|
match &self.command {
|
|
Command::OnRuntimeUpgrade(ref cmd) =>
|
|
commands::on_runtime_upgrade::on_runtime_upgrade::<Block, ExecDispatch>(
|
|
self.shared.clone(),
|
|
cmd.clone(),
|
|
config,
|
|
)
|
|
.await,
|
|
Command::OffchainWorker(cmd) =>
|
|
commands::offchain_worker::offchain_worker::<Block, ExecDispatch>(
|
|
self.shared.clone(),
|
|
cmd.clone(),
|
|
config,
|
|
)
|
|
.await,
|
|
Command::ExecuteBlock(cmd) =>
|
|
commands::execute_block::execute_block::<Block, ExecDispatch>(
|
|
self.shared.clone(),
|
|
cmd.clone(),
|
|
config,
|
|
)
|
|
.await,
|
|
Command::FollowChain(cmd) =>
|
|
commands::follow_chain::follow_chain::<Block, ExecDispatch>(
|
|
self.shared.clone(),
|
|
cmd.clone(),
|
|
config,
|
|
)
|
|
.await,
|
|
}
|
|
}
|
|
}
|
|
|
|
impl CliConfiguration for TryRuntimeCmd {
|
|
fn shared_params(&self) -> &sc_cli::SharedParams {
|
|
&self.shared.shared_params
|
|
}
|
|
|
|
fn chain_id(&self, _is_dev: bool) -> sc_cli::Result<String> {
|
|
Ok(match self.shared.shared_params.chain {
|
|
Some(ref chain) => chain.clone(),
|
|
None => "dev".into(),
|
|
})
|
|
}
|
|
}
|
|
|
|
/// Extract `:code` from the given chain spec and return as `StorageData` along with the
|
|
/// corresponding `StorageKey`.
|
|
pub(crate) fn extract_code(spec: &Box<dyn ChainSpec>) -> sc_cli::Result<(StorageKey, StorageData)> {
|
|
let genesis_storage = spec.build_storage()?;
|
|
let code = StorageData(
|
|
genesis_storage
|
|
.top
|
|
.get(well_known_keys::CODE)
|
|
.expect("code key must exist in genesis storage; qed")
|
|
.to_vec(),
|
|
);
|
|
let code_key = StorageKey(well_known_keys::CODE.to_vec());
|
|
|
|
Ok((code_key, code))
|
|
}
|
|
|
|
/// Get the hash type of the generic `Block` from a `hash_str`.
|
|
pub(crate) fn hash_of<Block: BlockT>(hash_str: &str) -> sc_cli::Result<Block::Hash>
|
|
where
|
|
Block::Hash: FromStr,
|
|
<Block::Hash as FromStr>::Err: Debug,
|
|
{
|
|
hash_str
|
|
.parse::<<Block as BlockT>::Hash>()
|
|
.map_err(|e| format!("Could not parse block hash: {:?}", e).into())
|
|
}
|
|
|
|
/// Check the spec_name of an `ext`
|
|
///
|
|
/// If the spec names don't match, if `relaxed`, then it emits a warning, else it panics.
|
|
/// If the spec versions don't match, it only ever emits a warning.
|
|
pub(crate) async fn ensure_matching_spec<Block: BlockT + serde::de::DeserializeOwned>(
|
|
uri: String,
|
|
expected_spec_name: String,
|
|
expected_spec_version: u32,
|
|
relaxed: bool,
|
|
) {
|
|
match remote_externalities::rpc_api::get_runtime_version::<Block, _>(uri.clone(), None)
|
|
.await
|
|
.map(|version| (String::from(version.spec_name.clone()), version.spec_version))
|
|
.map(|(spec_name, spec_version)| (spec_name.to_lowercase(), spec_version))
|
|
{
|
|
Ok((name, version)) => {
|
|
// first, deal with spec name
|
|
if expected_spec_name == name {
|
|
log::info!(target: LOG_TARGET, "found matching spec name: {:?}", name);
|
|
} else {
|
|
let msg = format!(
|
|
"version mismatch: remote spec name: '{}', expected (local chain spec, aka. `--chain`): '{}'",
|
|
name,
|
|
expected_spec_name
|
|
);
|
|
if relaxed {
|
|
log::warn!(target: LOG_TARGET, "{}", msg);
|
|
} else {
|
|
panic!("{}", msg);
|
|
}
|
|
}
|
|
|
|
if expected_spec_version == version {
|
|
log::info!(target: LOG_TARGET, "found matching spec version: {:?}", version);
|
|
} else {
|
|
log::warn!(
|
|
target: LOG_TARGET,
|
|
"spec version mismatch (local {} != remote {}). This could cause some issues.",
|
|
expected_spec_version,
|
|
version
|
|
);
|
|
}
|
|
},
|
|
Err(why) => {
|
|
log::error!(
|
|
target: LOG_TARGET,
|
|
"failed to fetch runtime version from {}: {:?}. Skipping the check",
|
|
uri,
|
|
why
|
|
);
|
|
},
|
|
}
|
|
}
|
|
|
|
/// Build all extensions that we typically use.
|
|
pub(crate) fn full_extensions() -> Extensions {
|
|
let mut extensions = Extensions::default();
|
|
extensions.register(TaskExecutorExt::new(TaskExecutor::new()));
|
|
let (offchain, _offchain_state) = TestOffchainExt::new();
|
|
let (pool, _pool_state) = TestTransactionPoolExt::new();
|
|
extensions.register(OffchainDbExt::new(offchain.clone()));
|
|
extensions.register(OffchainWorkerExt::new(offchain));
|
|
extensions.register(KeystoreExt(std::sync::Arc::new(KeyStore::new())));
|
|
extensions.register(TransactionPoolExt::new(pool));
|
|
|
|
extensions
|
|
}
|
|
|
|
/// Build a default execution that we typically use.
|
|
pub(crate) fn build_executor<D: NativeExecutionDispatch + 'static>(
|
|
shared: &SharedParams,
|
|
config: &sc_service::Configuration,
|
|
) -> NativeElseWasmExecutor<D> {
|
|
let wasm_method = shared.wasm_method;
|
|
let heap_pages = shared.heap_pages.or(config.default_heap_pages);
|
|
let max_runtime_instances = config.max_runtime_instances;
|
|
let runtime_cache_size = config.runtime_cache_size;
|
|
|
|
NativeElseWasmExecutor::<D>::new(
|
|
wasm_method.into(),
|
|
heap_pages,
|
|
max_runtime_instances,
|
|
runtime_cache_size,
|
|
)
|
|
}
|
|
|
|
/// Execute the given `method` and `data` on top of `ext`, returning the results (encoded) and the
|
|
/// state `changes`.
|
|
pub(crate) fn state_machine_call<Block: BlockT, D: NativeExecutionDispatch + 'static>(
|
|
ext: &TestExternalities,
|
|
executor: &NativeElseWasmExecutor<D>,
|
|
execution: sc_cli::ExecutionStrategy,
|
|
method: &'static str,
|
|
data: &[u8],
|
|
extensions: Extensions,
|
|
) -> sc_cli::Result<(OverlayedChanges, Vec<u8>)> {
|
|
let mut changes = Default::default();
|
|
let encoded_results = StateMachine::new(
|
|
&ext.backend,
|
|
&mut changes,
|
|
executor,
|
|
method,
|
|
data,
|
|
extensions,
|
|
&sp_state_machine::backend::BackendRuntimeCode::new(&ext.backend).runtime_code()?,
|
|
sp_core::testing::TaskExecutor::new(),
|
|
)
|
|
.execute(execution.into())
|
|
.map_err(|e| format!("failed to execute 'TryRuntime_on_runtime_upgrade': {}", e))
|
|
.map_err::<sc_cli::Error, _>(Into::into)?;
|
|
|
|
Ok((changes, encoded_results))
|
|
}
|
|
|
|
/// Same as [`state_machine_call`], but it also computes and prints the storage proof in different
|
|
/// size and formats.
|
|
///
|
|
/// Make sure [`LOG_TARGET`] is enabled in logging.
|
|
pub(crate) fn state_machine_call_with_proof<Block: BlockT, D: NativeExecutionDispatch + 'static>(
|
|
ext: &TestExternalities,
|
|
executor: &NativeElseWasmExecutor<D>,
|
|
execution: sc_cli::ExecutionStrategy,
|
|
method: &'static str,
|
|
data: &[u8],
|
|
extensions: Extensions,
|
|
) -> sc_cli::Result<(OverlayedChanges, Vec<u8>)> {
|
|
use parity_scale_codec::Encode;
|
|
use sp_core::hexdisplay::HexDisplay;
|
|
|
|
let mut changes = Default::default();
|
|
let backend = ext.backend.clone();
|
|
let proving_backend = InMemoryProvingBackend::new(&backend);
|
|
|
|
let runtime_code_backend = sp_state_machine::backend::BackendRuntimeCode::new(&proving_backend);
|
|
let runtime_code = runtime_code_backend.runtime_code()?;
|
|
|
|
let pre_root = backend.root().clone();
|
|
|
|
let encoded_results = StateMachine::new(
|
|
&proving_backend,
|
|
&mut changes,
|
|
executor,
|
|
method,
|
|
data,
|
|
extensions,
|
|
&runtime_code,
|
|
sp_core::testing::TaskExecutor::new(),
|
|
)
|
|
.execute(execution.into())
|
|
.map_err(|e| format!("failed to execute {}: {}", method, e))
|
|
.map_err::<sc_cli::Error, _>(Into::into)?;
|
|
|
|
let proof = proving_backend.extract_proof();
|
|
let proof_size = proof.encoded_size();
|
|
let compact_proof = proof
|
|
.clone()
|
|
.into_compact_proof::<sp_runtime::traits::BlakeTwo256>(pre_root)
|
|
.map_err(|e| format!("failed to generate compact proof {}: {:?}", method, e))?;
|
|
|
|
let compact_proof_size = compact_proof.encoded_size();
|
|
let compressed_proof = zstd::stream::encode_all(&compact_proof.encode()[..], 0)
|
|
.map_err(|e| format!("failed to generate compact proof {}: {:?}", method, e))?;
|
|
|
|
let proof_nodes = proof.into_nodes();
|
|
|
|
let humanize = |s| {
|
|
if s < 1024 * 1024 {
|
|
format!("{:.2} KB ({} bytes)", s as f64 / 1024f64, s)
|
|
} else {
|
|
format!(
|
|
"{:.2} MB ({} KB) ({} bytes)",
|
|
s as f64 / (1024f64 * 1024f64),
|
|
s as f64 / 1024f64,
|
|
s
|
|
)
|
|
}
|
|
};
|
|
log::info!(
|
|
target: LOG_TARGET,
|
|
"proof: {} / {} nodes",
|
|
HexDisplay::from(&proof_nodes.iter().flatten().cloned().collect::<Vec<_>>()),
|
|
proof_nodes.len()
|
|
);
|
|
log::info!(target: LOG_TARGET, "proof size: {}", humanize(proof_size));
|
|
log::info!(target: LOG_TARGET, "compact proof size: {}", humanize(compact_proof_size),);
|
|
log::info!(
|
|
target: LOG_TARGET,
|
|
"zstd-compressed compact proof {}",
|
|
humanize(compressed_proof.len()),
|
|
);
|
|
Ok((changes, encoded_results))
|
|
}
|
|
|
|
/// Get the spec `(name, version)` from the local runtime.
|
|
pub(crate) fn local_spec<Block: BlockT, D: NativeExecutionDispatch + 'static>(
|
|
ext: &TestExternalities,
|
|
executor: &NativeElseWasmExecutor<D>,
|
|
) -> (String, u32, sp_core::storage::StateVersion) {
|
|
let (_, encoded) = state_machine_call::<Block, D>(
|
|
&ext,
|
|
&executor,
|
|
sc_cli::ExecutionStrategy::NativeElseWasm,
|
|
"Core_version",
|
|
&[],
|
|
Default::default(),
|
|
)
|
|
.expect("all runtimes should have version; qed");
|
|
<sp_version::RuntimeVersion as Decode>::decode(&mut &*encoded)
|
|
.map_err(|e| format!("failed to decode output: {:?}", e))
|
|
.map(|v| {
|
|
let state_version = v.state_version();
|
|
(v.spec_name.into(), v.spec_version, state_version)
|
|
})
|
|
.expect("all runtimes should have version; qed")
|
|
}
|