Uh oh!
There was an error while loading. Please reload this page.
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.
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.
Error messages are misleading for equality cases.
The conditions now use
>=to reject equal values, but the error messages still show>. Whens.Height == next.Height, the message "invalid height: 10 > 10" is confusing because 10 is not greater than 10.Proposed fix to clarify error messages
func assertValid(s *RaftBlockState, next *RaftBlockState) error { if s.Height >= next.Height { - return fmt.Errorf("invalid height: %d > %d", s.Height, next.Height)+ return fmt.Errorf("invalid height: current %d >= next %d", s.Height, next.Height) } if s.Timestamp >= next.Timestamp { - return fmt.Errorf("invalid timestamp: %d > %d", s.Timestamp, next.Timestamp)+ return fmt.Errorf("invalid timestamp: current %d >= next %d", s.Timestamp, next.Timestamp) } return nil }📝 Committable suggestion
🤖 Prompt for AI Agents