try-runtime fast-forward panics

[liamaharon]

Description of bug

@alvicsam reported issues running fast-forward.

time cargo run --release --features try-runtime try-runtime \
            --runtime ./target/release/wbuild/"$NETWORK"-runtime/target/wasm32-unknown-unknown/release/"$NETWORK"_runtime.wasm \
            -lruntime=debug \
            --chain=${NETWORK}-dev \
            fast-forward --n-blocks ${N_BLOCKS} live --uri wss://${NETWORK}-try-runtime-node.parity-chains.parity.io:443
Is failing with error ERROR main runtime: panicked at 'Bitfields and heads must be included every block'.

I tried to reproduce the issue and got a different error:

$ ./target/debug/substrate try-runtime -lruntime=debug  --runtime=existing fast-forward --n-blocks 1 live --uri ws://localhost:9944

2023-04-05 18:42:17.254  INFO main try_runtime_cli::commands::fast_forward: Producing new empty block at height 52
2023-04-05 18:42:19.317 ERROR main runtime: panicked at 'Timestamp slot must match `CurrentSlot`', /Users/liamaharon/.cargo/git/checkouts/substrate-7e08433d4c370a21/7bbfe73/frame/babe/src/lib.rs:901:9
Error: Input("failed to execute 'BlockBuilder_apply_extrinsic': Execution aborted due to trap: wasm trap: wasm `unreachable` instruction executed\nWASM backtrace:\nerror while executing at wasm backtrace:\n    0: 0x54dfca - <unknown>!rust_begin_unwind\n    1: 0x5957 - <unknown>!core::panicking::panic_fmt::hf4a9df75710ece83\n    2: 0x446139 - <unknown>!<pallet_timestamp::pallet::Call<T> as frame_support::traits::dispatch::UnfilteredDispatchable>::dispatch_bypass_filter::{{closure}}::ha851ba02f996be58\n    3: 0x445d4b - <unknown>!environmental::local_key::LocalKey<T>::with::h02653259b8e2f653\n    4: 0x56567 - <unknown>!<polkadot_runtime::RuntimeCall as frame_support::traits::dispatch::UnfilteredDispatchable>::dispatch_bypass_filter::ha9b1507b34197eac\n    5: 0x5615d - <unknown>!<polkadot_runtime::RuntimeCall as sp_runtime::traits::Dispatchable>::dispatch::h82684c881496d7ad\n    6: 0x49bc2a - <unknown>!<sp_runtime::generic::checked_extrinsic::CheckedExtrinsic<AccountId,Call,Extra> as sp_runtime::traits::Applyable>::apply::h58a235af508c2822\n    7: 0x2f167b - <unknown>!frame_executive::Executive<System,Block,Context,UnsignedValidator,AllPalletsWithSystem,COnRuntimeUpgrade>::apply_extrinsic::hf434b1d1b7082e9b\n    8: 0x174d4b - <unknown>!BlockBuilder_apply_extrinsic")
2023-04-05 18:42:19.317  WARN main sp_state_machine::overlayed_changes::changeset: 1 storage transactions are left open by the runtime. Those will be rolled back.
2023-04-05 18:42:19.318  WARN main sp_state_machine::overlayed_changes::changeset: 1 storage transactions are left open by the runtime. Those will be rolled back.

Possibly similar to the bug that broke follow-chain (#13696)

[ggwpez]

Happening again in https://substrate.stackexchange.com/questions/9024.
Maybe we should add some warning or disable the command until its fixed?

[liamaharon]

#13887