-
Notifications
You must be signed in to change notification settings - Fork 129
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
Sync assertion / crash on invalid block #3043
Comments
Is there a way to reproduce that? As a side note, there are some important syncer changes missing on this branch. The only changes against the current syncer source code tree that make currently sense to me are with the worker/db.nim file. There is a potential problem with the error recovery after an import error (when there was an internal There is also a quick abort (for this sync scrum) useful when one can assume that the current scrum/sprint will fail at most or all blocks to be imported as it seems the case here. This will be updated when the |
Not sure, it happened a few hours after starting my mainnet node from an snapshot db (from November).. Of course, the fact that the block failed to apply is also an issue to be investigated, but that's a separate problem. |
What seemed to have happened was that the The assert came from a (reproducible) bookkeeping error when handling repeated import errors. |
to be clear, this is normal behavior - ie FC can switch to a different branch at any time and the syncer must make no assumptions about it. |
On the forked-layers branch (merged with master):
The text was updated successfully, but these errors were encountered: