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.

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

CRITICAL: Bitfields and heads must be included every block #2937

Closed
EclesioMeloJunior opened this issue Nov 11, 2022 · 2 comments
Closed

CRITICAL: Bitfields and heads must be included every block #2937

EclesioMeloJunior opened this issue Nov 11, 2022 · 2 comments
Assignees

Comments

@EclesioMeloJunior
Copy link
Member

Describe the bug

  • Running gossamer using the chain configuration westend-local I face the following critical log message
CRITICAL target=runtime message=panicked at 'Bitfields and heads must be included every block', /builds/runtime/parachains/src/paras_inherent/mod.rs:200:17	imports.go:L140:ext_logging_log_version_1

WARN     failed to handle slot 278029812: cannot finalise block: running runtime function: Failed to call the `BlockBuilder_finalize_block` exported function.

Additional Informations

  • I am using the latest changes in development branch
  • the config file I am using is:
[global]
basepath = "./tmp/westend"
log = "info"
metrics-address = ":9876"

[log]
core = ""
network = "trace"
rpc = ""
state = ""
runtime = ""
babe = ""
grandpa = ""
sync = "trace"
digest = ""

[init]
genesis = "./chain/westend-local/westend-local-spec-raw.json"

[account]
key = "bob"
unlock = ""

[core]
roles = 4
babe-authority = true
grandpa-authority = true
babe-lead = true

[network]
port = 7001
nobootstrap = false
nomdns = false

[rpc]
enabled = true
ws = true
port = 8545
host = "localhost"
modules = [
    "system",
    "author",
    "chain",
    "state",
    "rpc",
    "grandpa",
    "offchain",
    "childstate",
    "syncstate",
    "payment",
]
ws-port = 8546

[pprof]
listening-address = "localhost:6060"
block-rate = 0
mutex-rate = 0
@kishansagathiya
Copy link
Contributor

Can reproduce this. I will check what's causing this.

@qdm12
Copy link
Contributor

qdm12 commented Nov 22, 2022

Fixed by #2964

@qdm12 qdm12 closed this as completed Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants