-
Notifications
You must be signed in to change notification settings - Fork 112
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
Import failed: Slot number must increase #2636
Comments
I don't think this is related to secondary slot claiming. I have seen this happen for primary block as well. This has more to do with some time related inaccuracies. This error occurs only for the first slot in the epoch. gossamer/lib/babe/epoch_handler.go Line 88 in 3a471d9
we would not see the problem anymore. But that would mean that first slot would never get used, so that's bad. |
Different error
|
This might be the reason! But anyway I am seeing many of these errors, with or without |
@kishansagathiya I think this is not the reason, the error |
If you see |
🤔 hm, does this error you've reported here -> #2636 (comment) happened at the beginning of the sync when both peers start a connection? Or the error happened when peers were connected for some time exchanging blocks? |
Could you post some logs related to what is being decoded? I mean, I don't believe the error |
So, what I am noticing here is that substrate start a new epoch with the proposal of a particular block at epoch start slot. Let's say this is the xth block. Gossamer is able to import this block. But then gossamer also build a block at the same slot, but it builds (x+1)th block. I believe, gossamer should check the slot in the blocks that it imports. If gossamer believes that it is it's time to author a block, it should ignore the received block and instead of authoring x+1th block, it should author xth block. |
I was think about what can cause the above scenario.
|
Describe the bug
This block was created by the gossamer node:
The slot number specified in the error messages was claimed by the gossamer node as a secondary vrf slot in the epoch 6:
logs at https://gist.github.com/kishansagathiya/1bfbc988015a37c884beae7630a8169f
The text was updated successfully, but these errors were encountered: