Skip to content
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

Correct display of downtime in pcli validator query uptime #4442

Merged
merged 2 commits into from
May 24, 2024

Conversation

plaidfinch
Copy link
Collaborator

The downtime penalty is 0.01%, not 1% as previously displayed. This corrects the erroneous calculation which previously displayed an incorrect figure by a 100x factor.

Describe your changes

This adds a / 100.0 to correct the missing factor, and an explanatory comment.

Checklist before requesting a review

  • If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

    This is a display fix for pcli.

The downtime penalty is 0.01%, not 1% as previously displayed. This corrects the erroneous calculation which previously displayed an incorrect figure by a 100x factor.

Signed-off-by: plaidfinch <finch@starlingcyber.net>
@plaidfinch plaidfinch requested a review from conorsch May 23, 2024 07:02
@plaidfinch plaidfinch added A-client Area: Design and implementation for client functionality C-bug Category: a bug _P-low Priority: low labels May 23, 2024
Co-authored-by: katelyn martin <katelyn@penumbralabs.xyz>
Signed-off-by: Erwan Or <erwan.ounn.84@gmail.com>
@conorsch conorsch merged commit aa5b4e7 into main May 24, 2024
13 checks passed
@conorsch conorsch deleted the downtime-penalty-display-fix branch May 24, 2024 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-client Area: Design and implementation for client functionality C-bug Category: a bug _P-low Priority: low
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants