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
Simplify avalanche bootstrapping #2286
Simplify avalanche bootstrapping #2286
Changes from all commits
0128eaa
3bf262a
c88fb51
587204e
15cd71a
50ee5aa
f4d3809
79763e7
495846a
190d58f
e87d831
92baae2
7ac0792
b3fbe68
8f521cd
2b920aa
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
q: wouldn't this make stop vertex different for different nodes? Isn't this a problem that we linearize VMs in different nodes starting from different stop vertexes?
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.
avalanchego doesn't support DAGs other than the Fuji X-chain and the Mainnet X-chain. This code is here so that the local network X-chain will be immediately linearized (it is assumed that the DAG is empty in this case).
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.
I'd add this comment to the codebase
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.
q: why is this not
b.ForceAccepted(ctx, []ids.ID{stopVertexID})
?IIUC with b.ForceAccepted(ctx, nil) will start downloading missing vertexes, while stopVertexID is guaranteed to be already available locally
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.
will not download anything - as nothing is provided.
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.
I see that in ForceAccepted we append the vertexs found there with those missing already stored locally. So I understand that ForceAccepted may download something even if we pass ni here.
Also my question is: do we want to guarantee that a node download all accepted vertexes?
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.
We do (and must) guarantee that a node downloads all accepted vertices