BUGFIX: Grow log shows invalid values in edge cases #1872
Merged
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
d0sboots
reviewed
Jan 5, 2025
d0sboots
reviewed
Jan 8, 2025
Co-authored-by: David Walker <[email protected]>
catloversg
deleted the
pull-request/bugfix/grow-log-shows-invalid-values-in-edge-cases
branch
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.
In 23c862b, we fixed the case in which
ns.growreturns Infinity. On Discord, we received a report that terminal grow shows NaN%. When I checked the implementation ofprocessSingleServerGrowthand its callers, I found more bugs:ns.growshows "-100%".I carefully refactored code of
processSingleServerGrowthand its callers so that there is no behavior change inns.grow.Before:
After:
