Skip to content

Conversation

@holiman
Copy link
Contributor

@holiman holiman commented Apr 26, 2021

This PR removes a loop which we had in place to handle the case where people were upgrading from 1.8 to 1.9 during a fast-sync.
In 1.9, we started shoving old block data immediately into the freezer, whereas previously we wrote it to leveldb first.

@holiman holiman requested a review from fjl April 26, 2021 12:29
@fjl
Copy link
Contributor

fjl commented Apr 26, 2021

Weird. I tried this exact fix (pretty much), and some tests in package core failed for me.

Copy link
Member

@rjl493456442 rjl493456442 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm.

Perhaps we should consider writing genesis to freezer in other place? For example in the initialization. But it's just the nitpick.

And let's run the fast sync/snap sync/full sync to ensure it's not broken. We don't need to finish the entire sync, but just the beginning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants