Skip to content

add support for hot blocks #1

@kdembler

Description

@kdembler

Full log from the crash here: storage-squid.log. After the initial crash, the processor is stuck and not processing further blocks. @zeeshanakram3 suggested that this may be related to Subsquid feature that indexes un-finalized blocks and possibly rolls back to apply other blocks. This could explain why the squid on my laptop (which had a lot of pauses when syncing) didn't experience this and keeps syncing fine

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions