Due to creating a slice with the specified number of elements (rather
than a capacity hint), SafeParseIntSlice returned a slice with leading
zeros of length greater than was passed, rather than the correct value.
Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com>
Due to creating a slice with the specified number of elements (rather than a capacity hint),
SafeParseIntSlice
returned a slice with leading zeros of length greater than was passed, rather than the correct value.Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com>
Of course, the one function I didn't test has the bug... Thanks to @Gabrielopesantos in https://github.com/hashicorp/vault/pull/15561 for catching this!
@sgmiller We'll need to bump this in Vault on both 1.12.x and 1.11.x.