-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when parsing log file due to left pad track number #340
Comments
Thanks for reporting this issue. |
I'd suggest dropping the leading zero as I think that'd look more natural to end users looking at the outputted log? |
I agree. I've just fixed this issue in 4a53ecb. |
Right now, whipper left pads the track numbers out for the TOC and Tracks top-level entries in the YAML log such that each entry is of equal length. When parsing it, the YAML Spec specifies that the values 01 to 07 be treated as octals and thus how 08 and 09 parses is somewhat undefined as ends up implementation dependent.
Implementations tested:
Minimum example to test parsing:
The text was updated successfully, but these errors were encountered: