Fix encointer AURA slot

Open
#101 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
blockchain, testing

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.

Description

Something wrong, probably here:

https://github.com/paritytech/try-runtime-cli/blob/251438fec14dd2a39a129d5c893e653ec4e9cc89/core/src/common/empty_block/inherents/providers.rs#L126

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.

Dominant language
Rust
Stars
25
Forks
29
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from paritytech/try-runtime-cli

All issues in paritytech/try-runtime-cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.