-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
node: always start blocksync and avoid misconfiguration #8902
node: always start blocksync and avoid misconfiguration #8902
Conversation
Is blocksync intended to always be enabled in v0.35? It looks like the option is still present to disable it. |
I can't see a reason why you'd ever want to disable it, and nothing really changed in 0.36 to support force enabling it. |
@@ -700,10 +700,8 @@ func (n *nodeImpl) OnStart() error { | |||
} | |||
|
|||
if n.config.Mode != config.ModeSeed { | |||
if n.config.BlockSync.Version == config.BlockSyncV0 { |
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.
Maybe at this point we should just remove this setting from the config file entirely? At least at master and maybe in v0.36 that seems safe.
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 believe it's out in master and 0.36 this is just against 0.35
I don't think we should change this in the released version. |
This reverts commit 204281f.
Addresses: #8899