fix for client to skip the prove consistency request if checkpoint is unchanged #238
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…checkpoint is still the latest checkpoint
macovedj
approved these changes
Jan 4, 2024
lann
reviewed
Jan 4, 2024
| Cow::Borrowed(&ts_checkpoint.as_ref().checkpoint.log_root), | ||
| ) | ||
| .await?; | ||
| } |
There was a problem hiding this comment.
Does this allow the registry to rewind the checkpoint?
There was a problem hiding this comment.
That's a good point, I'll add another check and error for that in the client. Client should error if the registry checkpoint goes back in time.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Client will skip the prove consistency request if the previous checkpoint is still the latest checkpoint. This fixes an error when
fromandtoare the samelog_length.