-
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
TypeError on whipper offset find #263
Comments
Thanks for the bug report!
That's quite strange: could you provide a sample file file which shows this behaviour? Cheers, |
The problem is in my laptop being an old 32bit one and accuraterip_checksum not using the right data types for the operations there. See leo-bogert/accuraterip-checksum#2. |
Did you install
|
No, and I just see that the arch package uses the correct sources, but doesn't build accuraterip-checksum. It just uses the packaged version of it, which comes from leo-bogert's repo. I'll file a bug report there. So for here it boils down to whether the Exception that might result from |
It seems the package in Arch Linux's community repository was marked as
Uhm, if that step fails I think it's better to leave it failing hard (Exception) as I don't see a sensible recovery solution anyway... |
The most recent code of accuraterip-checksum at https://github.com/leo-bogert/accuraterip-checksum is fixed to work on 32 bit platforms. |
Please note that PR #274 would remove the dependency on an installed executable by converting accuraterip-checksum to a Python module. |
If the calculation of a checksum fails in
program/arc.py
,accuraterip_checksum
can returnNone
.command/offset.py
'sFind._arcs
fails in this case with a TypeError when trying to format theNone
as a number in its return value.(For context:
accuraterip_checksum
fails in my case due to anillegal hardware instruction
and dumping core when trying to compute a v2 checksum. Thus thereturncode
is nonzero and you might want to die with theTypeError
and not treat this as a bug.)The text was updated successfully, but these errors were encountered: