Skip to content

fix "block with unknown header is ready" error #2189

@noot

Description

@noot

Task summary

  • when syncing on the devnet, the error "block with unknown header is ready" shows up somewhat often
  • this really shouldn't be happening, as this means the handleReadyBlock function is being called with a block that isn't ready (ie. it's header isn't available to us)
  • the error is probably coming from tipSyncer.handleTick, as when handleReadyBlock is called from doSync, the block data is verified to already have headers

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions