You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
For future reference, for the time being we disabled processing of hot blocks and that has indeed resolved the issue. Reasoning is that Orion doesn't handle hot blocks so doing that only in storage squid will not bring any real UX improvement.
kdembler
changed the title
bug: corrupted state and processor stuck
add support for hot blocks
Jan 16, 2024
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
The text was updated successfully, but these errors were encountered: