Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
genesis: add support for arbitrary initial height #5191
genesis: add support for arbitrary initial height #5191
Changes from all commits
35c8a7c
31622cb
110576f
9a0156f
d9d91b5
77bfbee
3e4713c
19ebc3c
31b9154
7a83f4f
9024238
37ea68c
5492bda
5b07bcf
3117ee3
6ce918e
0ba502a
06941fa
7a6c109
f2b46f3
e2f3767
5f0516d
9f119f2
2d1ac9c
01163ce
4d8f8f1
12bb951
f0dac40
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Large diffs are not rendered by default.
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.
Isn't this immutable? Maybe we can load it once upfront and then not need to worry about the mutex?
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.
Yeah, but I figured that'd be premature optimization unless we could demonstrate that there was actual mutex contention -- complexity (i.e. caching) is usually far more likely to cause problems. Although I suppose storing this during
consensus.NewState()
would pretty much always do the right thing.Opened #6012, we can have a look after the refactor.
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.
Note, this was changed to a read-lock in the consensus reactor p2p refactor.