Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Don't allow user to call startprovisioner or startblockgenerator when still syncing #13

Closed
jules opened this issue Aug 12, 2019 · 1 comment
Closed

Don't allow user to call startprovisioner or startblockgenerator when still syncing #13

jules opened this issue Aug 12, 2019 · 1 comment
Assignees
@jules
Labels
type:bug Something isn't working

Comments

@jules
Copy link
Contributor

jules commented Aug 12, 2019

As discussed in #7, if a user calls startprovisioner while syncing, it could lead to their provisioner components starting on an obsolete round, and getting stuck with no proper feedback for the user. The node should disallow the use of startprovisioner until we are sure the node is at the tip of the chain.
@jules jules added the type:bug Something isn't working label Aug 12, 2019
@jules jules self-assigned this Aug 12, 2019
@jules jules changed the title Don't allow user to call startprovisioner when still syncing Don't allow user to call startprovisioner or startblockgenerator when still syncing Aug 15, 2019
@jules
Copy link
Contributor Author

jules commented Aug 19, 2019

Closing this, as we are changing the node to no longer require the user to start up consensus.

@jules jules closed this as completed Aug 19, 2019
@jules jules mentioned this issue Aug 19, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jules jules

Labels
type:bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jules