-
Notifications
You must be signed in to change notification settings - Fork 89
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
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
Comments
JoeLametta
changed the title
Fix regression introduced in #411
Fix regression introduced due to Python 3 port
Nov 26, 2019
|
JoeLametta
added
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
labels
Dec 4, 2019
hydrian
pushed a commit
to hydrian/whipper
that referenced
this issue
Dec 18, 2019
Fixes whipper-team#424. Signed-off-by: JoeLametta <JoeLametta@users.noreply.github.com> Signed-off-by: hydrian <ben.tyger@tygerclan.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
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: