-
Notifications
You must be signed in to change notification settings - Fork 197
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
bugFix/shuffle-out-epoch-1-restart #2016
Conversation
…hinks it should start in epoch 0.
epochStart/bootstrap/process.go
Outdated
@@ -339,7 +339,10 @@ func (e *epochStartBootstrap) Bootstrap() (Parameters, error) { | |||
return Parameters{}, err | |||
} | |||
|
|||
if e.isStartInEpochZero() || e.computeIfCurrentEpochIsSaved() { | |||
isStartInEpochZero := e.isStartInEpochZero() | |||
isCurrentEpochIsSaved := e.computeIfCurrentEpochIsSaved() |
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.
*isCurrentEpochSaved
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.
+1
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.
System tests passed.
edge case fix when reshuffling in early epoch 1, the node currently thinks it should start in epoch 0.