-
Notifications
You must be signed in to change notification settings - Fork 202
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
[sovereign] Disable notifier registration until fully synced #6571
[sovereign] Disable notifier registration until fully synced #6571
Conversation
log.Debug("notifierBootstrapper.checkNodeState: worker's go routine is stopping...") | ||
return | ||
case <-nb.nodeSyncedChan: | ||
err := nb.sovereignNotifier.RegisterHandler(nb.incomingHeaderHandler) |
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.
this is quite a problem is register is failing.
Can't we design in such a way that the node stops ?
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.
Changed it as requested to signal the node to stop if registration fails
…MX-15963-disable-notifier-until-synced
The base branch was changed.
deaafbd
into
feat/sovereign-mainchain-header-sync
Reasoning behind the pull request
Proposed changes
notifierBootstrapper
which will start waiting on a go routine to be notified via nodeSyncedChan when the sovereign node is synced. Meanwhile, it will print the current node state in log. When node is fully synced, it will register the incoming header processor to the websocket listener and exit the waiting loop.Testing procedure
Pre-requisites
Based on the Contributing Guidelines the PR author and the reviewers must check the following requirements are met:
feat
branch created?feat
branch merging, do all satellite projects have a proper tag insidego.mod
?