Fix regression introduced due to Python 3 port #424
Labels
Accepted
Accepted issue on our roadmap
Bug
Generic bug: can be used together with more specific labels
Regression
Bug that breaks functionality known to work in previous releases
Milestone
After manual testing of this port, I've found a regression (everything else appears to be working fine).
Output:
Debug log:
Code of the relevant section:
whipper/whipper/image/table.py
Lines 799 to 825 in f6dcc08
It seems that the
offset
is a float (int.0
).The value of the
offset
comes either fromoffset = self.getTrackStart(track.number)
, relevant code here:whipper/whipper/image/table.py
Lines 194 to 203 in f6dcc08
or from
offset = self.getTrackEnd(self.tracks[-1].number) + 1
, relevant code here:whipper/whipper/image/table.py
Lines 205 to 227 in f6dcc08
In both cases what's alarming is that the float value seems to originate from the
self.tracks[number].getIndex(index).absolute
call. I don't know why that one is a float but it should be an int.If I run the same command using whipper's code from
develop
branch (commit f740a0e) against the same files, it completes successfully.This can be replicated using the files included in this ZIP archive but I don't think it depends on these specific files.
Originally posted by @JoeLametta in #411 (comment)
The text was updated successfully, but these errors were encountered: