-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
Description of problem:
Currently used yaml library uses Go's ParseInt and ParseUInt functions. Because 0451 has leading 0, it is being interpreted as octal and the value deserialized as 297 instead of (0)451. Value like 0781 is parsed correctly by accident: '8' is invalid in octal (0-7), so after Parse(U)Int fail, it's parsed by other function.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Try use USB device with GDP that has one of the IDs starting with 0 and is valid octal number.
Actual results:
GDP looks for a different device
Expected results:
The number is deserialized correctly as hexdec despite leading 0.
Additional info: