invalid argument "0x86" for "-u, --data" flag: strconv.ParseUint: parsing "0x86": invalid syntax

[flowexp]

Hi,

I am writing a program using cobra and pflag.
There is one option as below:
cmd.Flags().UintSliceVarP(&data, "data", "u", []uint{}, "write data separated by ,")

I expect it can accept integer data list no matter decimal or hexadecimal format.
But below error reported when using hex data.
There is no such kind of problem when using Int32SliceVarP or Int64SliceVarP.
By the way, actually I need Uint32SliceVarP, but seems it is not supported yet.

fexp haps write_umrbus -u 0x86
Error: invalid argument "0x86" for "-u, --data" flag: strconv.ParseUint: parsing "0x86": invalid syntax
Usage:
fexp haps write_umrbus [flags]

Flags:
-b, --bus uint32 umrbus bus number (default 1)
-u, --data uints write data seperated by , (default [])
-d, --device uint32 umrbus device number (default 8)
-h, --help help for write_umrbus
-i, --id uint32 umrbus capim address (default 1)

Global Flags:
-s, --host string server host name (default "localhost")
-p, --port uint32 server port number (default 60066)
-v, --verbose show verbose information

invalid argument "0x86" for "-u, --data" flag: strconv.ParseUint: parsing "0x86": invalid syntax

Guofu

[tomasaschan]

This issue has not been updated in a long time. Is it still relevant?

(If I receive no answer before the end of the summer, I'll close it. Feel free to re-open if you come here after that happens and it is relevant to you - but if you do, please also comment and specify what outcome you're interested in!)

[happysnaker]

Opened #484 to make UintSlice accept Go-style base prefixes like 0x86, matching the behavior of the other integer slice flags. The patch switches UintSlice parsing to base autodetection and adds regression coverage for hexadecimal input.

[happysnaker]

Follow-up: I opened #484 for this. The change allows UintSlice entries such as 0x86 by switching to base-0 parsing, matching Go's ordinary integer literal handling.