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
Currently library doesn't have support for millibyte. But if you use involuntarily (let's say data comes from external API), it calculates millibyte as megabyte for the following code: normalized_unit.startswith(unit.decimal.symbol[0].lower())).
Do you have any plan to add support for millibyte?
The text was updated successfully, but these errors were encountered:
+1 This is a concern for my use case which is in Kubernetes deployment manifests. CPU resources for containers are mentioned in m which is milli not Mega.
Currently library doesn't have support for millibyte. But if you use involuntarily (let's say data comes from external API), it calculates millibyte as megabyte for the following code: normalized_unit.startswith(unit.decimal.symbol[0].lower())).
Do you have any plan to add support for millibyte?
The text was updated successfully, but these errors were encountered: