paritytech / paritytech/try-runtime-cli
Fix encointer AURA slot
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Something wrong, probably here:
panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cumulus-pallet-aura-ext-0.15.0/src/consensus_hook.rs:69:9:
assertion `left == right` failed: slot number mismatch
left: Slot(143998834)
right: Slot(287997668)
thread 'main' panicked at cli/main.rs:326:10:
Looks like it is off by 2x, occurred here: https://github.com/polkadot-fellows/runtimes/actions/runs/11168344347/job/31047391625?pr=463
We do have the --blocktime flag, but i think its not being used here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in core/src/common/empty_block/inherents/providers.rs around line 126 and trace how the --blocktime flag reaches the AURA inherents provider. Use the linked runtimes workflow failure to reproduce the slot mismatch. Done means the encointer AURA slot matches the expected slot when the configured block time is used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100