fix(ui): correct Y-axis tick precision on Docker memory chart#2027
Open
svenvg93 wants to merge 1 commit into
Open
fix(ui): correct Y-axis tick precision on Docker memory chart#2027svenvg93 wants to merge 1 commit into
svenvg93 wants to merge 1 commit into
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
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
Fix incorrect Y-axis tick label precision on the Docker/Podman Memory Usage chart. Because container memory is stored in MB, the raw value (
val) was always ≥ 10, sotoFixedFloatwas always called with 0 decimal places. This caused values in the 1–10 GB range to be rounded to the nearest whole GB, producing duplicate and misleading tick labels (e.g. both 1.2 GB and 1.5 GB displaying as "1 GB", and 1.8 GB displaying as "2 GB"), making the axis appear non-linear.Also corrects a wrong JSDoc comment on the container
Statstype — memory is in MB, not GB.closes #2026
🪵 Changelog
🔧 Fixed