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
The Kubernetes resource requirements can specify petabyte and exabyte (and similar binary) unit suffixes. Currently units.parse_bytes only goes up to T/Ti. We should extend units.parse_bytes to support larger units. The implementation should also be modified to avoid use of strconv.ParseInt which is limited to 64-bit integers. Use the big/int package instead.
Previous changes to the built-in function to use big.Int et al. had
been made without knowledge of these missing units. So, here they are.
Fixesopen-policy-agent#2911.
Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>
Previous changes to the built-in function to use big.Int et al. had
been made without knowledge of these missing units. So, here they are.
Fixes#2911.
Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>
dolevf
pushed a commit
to dolevf/opa
that referenced
this issue
Nov 4, 2021
Previous changes to the built-in function to use big.Int et al. had
been made without knowledge of these missing units. So, here they are.
Fixesopen-policy-agent#2911.
Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>
Signed-off-by: Dolev Farhi <farhi.dolev@gmail.com>
The Kubernetes resource requirements can specify petabyte and exabyte (and similar binary) unit suffixes. Currently
units.parse_bytes
only goes up to T/Ti. We should extendunits.parse_bytes
to support larger units. The implementation should also be modified to avoid use ofstrconv.ParseInt
which is limited to 64-bit integers. Use thebig/int
package instead.The text was updated successfully, but these errors were encountered: