-
Notifications
You must be signed in to change notification settings - Fork 877
Allow for sync state where batch is unknown #7391
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
base: unstable
Are you sure you want to change the base?
Conversation
} else { | ||
return Err(RemoveChain::WrongChainState(format!( | ||
"Batch not found for current processing target {}", | ||
self.processing_target |
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 will be a rare event, should we add a debug log? If we ever wonder why the SyncingChain is not processing anything
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.
Yeah good call.
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 don't think it will ever stop processing, something will progress it, but agree a log would be handy
This pull request has merge conflicts. Could you please resolve them @AgeManning? 🙏 |
Some required checks have failed. Could you please take a look @AgeManning? 🙏 |
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.
LGTM
#7360 shows a bug where we attempt to process a batch that is not existent.
It can be non-existent for two reasons:
Under these conditions, the chain will be removed because there process_id pointer doesn't point to a batch.
This PR permits this state, by simply removing the error catch.