[proto] Remove redundant RPC GetLastCommittedBlockNumber() #155
Conversation
This file contains hidden or 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
Signed-off-by: Liran Funaro <[email protected]>
cendhu
reviewed
Nov 6, 2025
There was a problem hiding this comment.
My suggestion is to use the name GetLastCommittedBlockNumber instead of GetNextExpectedBlockNumber. This also aligns with the existing SetLastCommittedBlockNumber. The caller (i.e., the sidecar) can then derive the next expected block number from the last committed block number.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Type of change
Description
GetLastCommittedBlockNumber()- It was already covered byGetNextExpectedBlockNumber()GetNextExpectedBlockNumber()- The sidecar verifies this anyway before calling this methodGetLastCommittedBlockNumber()withGetNextExpectedBlockNumber()Related issues