Questions tagged [try-runtime]
The try-runtime tag has no usage guidance.
36
questions
0
votes
1
answer
20
views
pallet storage migration fails try-runtime idempotent test
Some of the pallets storage migrations fail the idempotent test because in the pre_upgrade method there is an ensure! check to make sure that the current storage version is the one that applies for ...
- 109
1
vote
2
answers
49
views
Integrating storage migration for pallet-contracts
When integrating pallet-contracts v10 storage migration in pub type Migrations
use pallet_contracts::migration::{v10, v11, v12};
pub type Migrations = (
v10::Migration<Runtime>,
)
I get an ...
- 1,080
1
vote
1
answer
29
views
Do I need to run a pallet storage migrations even when I'm just adding the pallet to the runtime for the first time?
Do I need to run a pallet storage migrations even when I'm just adding the pallet to the runtime for the first time?
This question came up because while testing the upgrade using the try-runtime cli, ...
- 109
1
vote
1
answer
18
views
Can the spec_name of the RuntimeVersion be changed on a runtime upgrade?
Can the spec_name of the RuntimeVersion be changed on a runtime upgrade? And if so, can the check performed by the try-runtime cli that the spec_names have to match be disabled?
- 109
0
votes
0
answers
11
views
not all trait items implemented, missing: `score_update_worst_case`
I am unable to build try-runtime features.
My command: cargo build --features try-runtime --release
My issue:
impl<T: Config> SortedListProvider<T::AccountId> for UseValidatorsMap<T&...
- 616
2
votes
1
answer
57
views
Try runtime failed to generate compact proof: TrieError(InvalidStateRoot
In a recent upgrade of substrate try-runtime begun to return errors and fault which could previously be ignored started to catch my attention.
What could be possible sources of this problem:
[2023-10-...
- 1,080
1
vote
2
answers
74
views
How to debug try-runtime with the new try-runtime client?
I'm trying to attach the lldb debugger (from VS Code) to the new try-runtime client. However the breakpoints I setup inside the chain code on on_upgrade are never reached (Obliviously because they are ...
- 1,080
1
vote
1
answer
19
views
try-runtime error exceeded max limit of 15728640
I am receiving the following error when I run try-runtime:
[2023-10-28T09:07:02Z ERROR remote-ext] Error = Call(Custom(ErrorObject { code: ServerError(-32702), message: "Response is too big",...
- 8,130
0
votes
0
answers
38
views
How to fix try-runtime execution aborted issue?
Trying to do a try-runtime in a test node using the command -
try-runtime --runtime ./target/release/wbuild/alphanet-runtime/alphanet_runtime.wasm on-runtime-upgrade live --uri ws://IP:PORT
and ...
- 759
0
votes
1
answer
36
views
Try-runtime error, runtime is NOT compiled with try-runtime feature
I am struggling with following error, any thoughts what can cause it? I am compiling WASM blob with following command:
cargo build --release --features try-runtime --package frontier-template-runtime ...
- 111
4
votes
1
answer
33
views
substrate | try-runtime | sub-command | "fast-forward" | "ERROR main runtime: panicked at 'Timestamp slot must match `CurrentSlot`'"
I am currently in the process of integrating and testing the "try-runtime" feature on Starknet Madara.
https://github.com/keep-starknet-strange/madara/pull/690
However, I have encountered ...
- 41
1
vote
2
answers
53
views
How to use try-runtime when upgrading a chain/parachain to latest substrate release?
What is the best practice regarding try-runtime, what errors and warnings should one look out for in the output.
When upgrading a chain it is good practice to try to execute storage migration before ...
- 1,080
4
votes
1
answer
101
views
trait bounds not satisfied with Executive::try_runtime_upgrade()
I'm attempting to integrate try-runtime into substrate-contracts-node and I get the following error when I call Executive::try_runtime_upgrade():
Compiling contracts-node-runtime v0.24.0 (/Users/bruno/...
- 8,130
1
vote
1
answer
51
views
How to use the follow-chain subcommand in try-runtime?
In the try-runtime documentation, there is note of a follow-chain subcommand which follows the given chain’s finalized blocks and apply all of its extrinsics.
There are also some examples here.
I ...
- 8,130
1
vote
1
answer
66
views
Running try-runtime with try-state option doesn't fail
When running the following command the try-state fails as it should(I purposefully made the try-state for the Collective pallet incorrect so that it fails):
./substrate-try-runtime try-runtime \
--...
- 603
1
vote
1
answer
51
views
Problem when running try-state
I have been trying to run the try-state hook to check whether the Polkadot network passes all the checks.
I started a local node and imported the state from the Polkadot network.
When trying to run ...
- 603
2
votes
2
answers
107
views
Getting 'Bad input data provided to execute_block' when running try-runtime's follow-chain
When I use the follow-chain subcommand I am getting the following error:
2023-03-17 16:22:15.698 ERROR main runtime: panicked at 'Bad input data provided to execute_block: Codec error', /Users/bruno/...
- 8,130
3
votes
1
answer
171
views
How to log in try-runtime?
#[cfg(feature = "try-runtime")]
fn pre_upgrade() -> Result<Vec<u8>, &'static str> {
log::info!("Pre-check account: {ERROR_ACCOUNT}");
let a = ...
- 9,474
0
votes
1
answer
43
views
try-runtime polkadot version 36 .. execution flag removed
we try to execute try-runtime command in this way
cargo run --release --features=try-runtime,mangata-rococo try-runtime --chain=public-testnet --execution=Native on-runtime-upgrade live --uri wss://...
- 361
2
votes
1
answer
107
views
AllPalletsWithSystem trait not implemented for Executive when running tests
I'm migrating a project from substrate-node-template to substrate-parachain-template and I'm encountering an issue when running tests. I understand that this is completely dependent of my local code ...
- 187
2
votes
1
answer
43
views
try-state runtime-level hook
We've been trying to use the new try_state hook. However, a significant limitation seems to be that this hook is only accessible from the individual pallets. We want to add some checks that depend on ...
- 372
2
votes
3
answers
63
views
try-runtime fails with error RestartNeeded - Invalid request ID
I am trying to run try-runtime locally to see the execution results of a particular storage migration, using live subcommand to upload a production state from a remote node.
I am getting an error: ...
- 354
1
vote
1
answer
31
views
failed to execute TryRuntime_on_runtime_upgrade: Runtime panicked (Update to 0.9.31 version)
Once we updated to version 0.9.31 and run try-runtime feature
cargo run --release --features=try-runtime,mangata-rococo try-runtime --chain=public-testnet --execution=Native on-runtime-upgrade live --...
- 361
3
votes
1
answer
267
views
Testing a migration with `try-runtime`
I have written a migration for the phragmen pallet in Substrate and now I want to test it. I would want to use the current state of Kusama/Polkadot to make sure the migration works correctly. To ...
- 603
3
votes
1
answer
98
views
Polkadot 29 update - try-runtime feature (trait bounds error)
We are doing upgrade to polkadot version 29. Everything works fine until we run the command
cargo build -r --features try-runtime
we got error trait bounds. In this version there was change from ...
- 361
5
votes
0
answers
62
views
How to determine if a parachain runtime migration is too big?
I want to write runtime storage migration for our parachain. This time it will scan large storage maps with more than 10k entries. This may results in very large PoV block size. I'm wondering what the ...
- 717
3
votes
1
answer
74
views
Potential storage issue with try-runtime tool
Hey guys I'm seeing a weird thing with the following migration code:
pub struct SomeMigration;
impl OnRuntimeUpgrade for SomeMigration {
fn on_runtime_upgrade() -> Weight {
let ...
1
vote
1
answer
79
views
What is a good use-case for using try-runtime with follow-chain and fork-off-substrate?
In the docs I see the following:
You can combine try-runtime with fork-off-substrate to test your chain
before production. Use try-runtime to test your chain's migration and
its pre and post states. ...
- 8,130
0
votes
1
answer
37
views
try-runtime: panicked at version mismatch
I am running the node-template on ws://localhost:9944 and I am running the following command on Substrate:
cargo run --release --features=try-runtime try-runtime on-runtime-upgrade live -u ws://...
- 8,130
0
votes
1
answer
18
views
try-runtime: Found argument 'ws://localhost:9944' which wasn't expected
I run the following command:
cargo run --release --features=try-runtime try-runtime on-runtime-upgrade live ws://localhost:9944
And I get the error:
error: Found argument 'ws://localhost:9944' which ...
- 8,130
0
votes
1
answer
82
views
`try-runtime` doesn't start with a proper state
Context:
Testing try-runtime::follow-chain utility with a local live chain.
Problem:
RemoteExternalities doesn't create a perfect copy of the state.
After follow-chain connects to a node, it starts ...
- 234
1
vote
1
answer
86
views
try-runtime no output
When trying to run try-runtime I do not get any logs. I also received an error in my local node:
2022-07-28 14:42:57 Accepting new connection, 1/100
2022-07-28 14:42:57 WS error: i/o error: Transport ...
- 153
1
vote
1
answer
56
views
No output from `try-runtime`
When running try-runtime I do not get any logs/output. Even when specifying explicitly RUST_LOG=runtime=trace,try-runtime::cli=trace,executor=trace, still there is silence. However, in case of failure ...
- 234
6
votes
2
answers
121
views
best practice to test a runtime with large chain state before runtime upgrade?
As the chain state goes larger and larger, it gets hard to export/fetch the chain state.
Are there any other tools aside from fork-off-substrate and try-runtime for performing a runtime migration?
- 9,474
4
votes
1
answer
230
views
Removal of storage prefix from database
I am currently writing a migration to remove a pallet and all its memory from our runtime. Unfortunately, I cannot manage to check for the existence of the pallet's prefix in the pre- and post upgrade ...
8
votes
1
answer
320
views
"wasm32-unknown-unknown target is not supported"-error while integrating try-runtime
Using this guide to integrate try-runtime on my node i get the error about get random not building for wasm.
error: the wasm32-unknown-unknown target is not supported by default, you may need to ...
- 1,080