Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update 'time' in Cargo.lock to resovle build error #92

Merged
merged 3 commits into from
Sep 10, 2024
Merged

Update 'time' in Cargo.lock to resovle build error #92

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b9fdbba
Update 'time' in Cargo.lock to resovle build error
jsdw Aug 12, 2024
6cb8089
New clippy formatting
ggwpez Sep 10, 2024
46a97b2
fmt
ggwpez Sep 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 12 additions & 4 deletions Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

20 changes: 11 additions & 9 deletions cli/main.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,10 +20,12 @@
//! Substrate's programmatic testing framework.
//!
//! > 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/client/runtime interactions, and the runtime apis work in the
//! substrate runtime, before commencing to working with `try-runtime`.
//! > 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/client/runtime interactions, and the runtime apis work in
//! > the
//! > substrate runtime, before commencing to working with `try-runtime`.
//!
//! #### Resources
//!
Expand Down Expand Up @@ -176,9 +178,9 @@
//!
//! For the following examples, we assume the existence of the following:
//!
//! 1. a substrate node compiled with `--features try-runtime`, called `substrate`. This will be
//! the running node that you connect to, and provide a wasm blob that has try-runtime
//! functionality enabled.
//! 1. a substrate node compiled with `--features try-runtime`, called `substrate`. This will be the
//! running node that you connect to, and provide a wasm blob that has try-runtime functionality
//! enabled.
//! 2. the `try-runtime` CLI binary on your path.
//!
//! ```bash
Expand All @@ -200,8 +202,8 @@
//! ```
//!
//! * Same as the previous example, but run it at specific block number's state and using the live
//! polkadot network. This means that this block hash's state should not yet have been pruned by the
//! node running at `rpc.polkadot.io`.
//! polkadot network. This means that this block hash's state should not yet have been pruned by
//! the node running at `rpc.polkadot.io`.
//!
//! ```bash
//! try-runtime \
Expand Down
Loading