-
Notifications
You must be signed in to change notification settings - Fork 664
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
fix: disable epoch info gc for now #2952
Conversation
@Kouprin can you help fix the store validator code? |
@bowenwang1996 please check if could we enable
|
@Kouprin I don't see why we cannot enable it. Do you want to do it in another PR or in this one? |
I have no preferences. It might be better to have a separate PR as for another purpose but it's up to you. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Undo the Cargo.lock
change
@SkidanovAlex no Cargo.lock change after merging with master :) |
Currently we would garbage epoch information right after the epoch switch, which causes many problems including rpc not able to fetch chunks/blocks in the past epoch, not able to verify blocks in the past epoch, etc. I think it is safer to disable it for now and maybe consider implementing it properly when we redo the syncing code.
Currently we would garbage epoch information right after the epoch switch, which causes many problems including rpc not able to fetch chunks/blocks in the past epoch, not able to verify blocks in the past epoch, etc. I think it is safer to disable it for now and maybe consider implementing it properly when we redo the syncing code.
Currently we would garbage epoch information right after the epoch switch, which causes many problems including rpc not able to fetch chunks/blocks in the past epoch, not able to verify blocks in the past epoch, etc. I think it is safer to disable it for now and maybe consider implementing it properly when we redo the syncing code.