-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[Bug] Fix Setting#byteSizeSetting to use whole value string #9011
Conversation
This fixes a bug where the Setting#byteSizeSetting static method returned fractional byte values when calling .toString inside the lambda. The change is to directly return the bytes value as a string instead of using ByteSizeValue#toString which tries to be smart and by pretty printing in a more human-friendly format. Signed-off-by: Nicholas Walter Knize <[email protected]>
Signed-off-by: Nicholas Walter Knize <[email protected]>
This is currently blocking passing builds on main. |
@reta mind giving this a quick once over and approval so we can unblock test failures? |
Gradle Check (Jenkins) Run Completed with:
|
Codecov Report
@@ Coverage Diff @@
## main #9011 +/- ##
============================================
+ Coverage 71.02% 71.05% +0.03%
- Complexity 57210 57268 +58
============================================
Files 4764 4764
Lines 270156 270153 -3
Branches 39532 39532
============================================
+ Hits 191887 191967 +80
+ Misses 62100 62056 -44
+ Partials 16169 16130 -39
|
Gradle Check (Jenkins) Run Completed with:
|
I'm going to go ahead and YOLO merge this to unblock the failures on main. |
@nknize was about to say LGTM except for change log. Can you add a change log entry in your next commit? |
Or I see skip-changelog was specifically added.... okay... |
Yeah.. This changelog mechanism is pretty broken. 😕 I can go back and add an entry for this if you think it's really needed. |
…ch-project#9011) This fixes a bug where the Setting#byteSizeSetting static method returned fractional byte values when calling .toString inside the lambda. The change is to directly return the bytes value as a string instead of using ByteSizeValue#toString which tries to be smart and by pretty printing in a more human-friendly format. Signed-off-by: Nicholas Walter Knize <[email protected]> Signed-off-by: Kaushal Kumar <[email protected]>
…ch-project#9011) This fixes a bug where the Setting#byteSizeSetting static method returned fractional byte values when calling .toString inside the lambda. The change is to directly return the bytes value as a string instead of using ByteSizeValue#toString which tries to be smart and by pretty printing in a more human-friendly format. Signed-off-by: Nicholas Walter Knize <[email protected]> Signed-off-by: Ivan Brusic <[email protected]>
…ch-project#9011) This fixes a bug where the Setting#byteSizeSetting static method returned fractional byte values when calling .toString inside the lambda. The change is to directly return the bytes value as a string instead of using ByteSizeValue#toString which tries to be smart and by pretty printing in a more human-friendly format. Signed-off-by: Nicholas Walter Knize <[email protected]> Signed-off-by: Shivansh Arora <[email protected]>
This fixes a bug where the
Setting#byteSizeSetting
static method returned fractional byte values when calling.toString
inside the lambda. The change is to directly return the bytes value as a string instead of usingByteSizeValue#toString
which tries to be smart and pretty print in a more human-friendly format.closes #9010
relates #9005