You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 15ba5f5
Browse filesBrowse the repository at this point in the historyBrowse files
app: show container RAM usage with a unit per side, fastfetch style
The RAM chip on the running-container cards, and the same text on the
details screen, printed whole megabytes on both sides: "1/1536 MB (0%)".
Now each side picks its own unit with two decimals, spaced the way
fastfetch prints memory: "13.50 MB / 1.50 GB (1%)", and a container
idling below a megabyte reads in KB instead of "0 MB". Without a limit
the chip stays used-only, "13.50 MB (0.2%)" of the host's RAM, as before.
The backend already sends kilobytes; the app threw the precision away
when it stored megabytes in OSInfo. Keep the kilobytes and format them
through a new ResourceLimits.formatMemoryUsage(). The limit chip and the
config form keep formatMemory()'s round "128 MB" / "1.5 GB" look, since a
slider label with two decimals would only add noise.
The two string resources change argument type from %d to %s, and a
stale translation of the old key would make getString() throw, so they
are new keys and the old ones are dropped from every locale.
Signed-off-by: ravindu644 <droidcasts@protonmail.com>
0 commit comments