docs(validator): clarify circuit breaker comments to match >= conditions #15930
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
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.
description
My PR makes small documentation and formatting improvements in
circuitBreakBuilder:Clarified comments – comments now explicitly mention that circuit breaker conditions trigger when missed slots are greater than or equal to (
>=) the configured limits, matching the actual logic.Normalized spacing – replaced a few non-breaking spaces (U+00A0) that had accidentally appeared in the log field alignment (e.g.
"currentSlot": s).These invisible characters sometimes come from copy-paste in editors and can cause formatting inconsistencies or minor linting issues.
They were replaced with regular ASCII spaces to ensure clean formatting and consistent
go fmtbehavior.(source)