-
Notifications
You must be signed in to change notification settings - Fork 90
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
whipper offset find exception #208
Comments
It seems that whipper checks if there are AccurateRip's responses but only warns if there are none. Instead of just warning, in case there are no responses, it should inform the user and quit. |
I think this issue has been solved in whipper |
I am having this same issue in version 0.7.2. I have a debug log here, should I start a new issue? Thanks!
|
Reopened, thanks for the issue report! |
Confirmed: whipper should abort the offset find operation if no remote AccurateRip entries are found... whipper/whipper/command/offset.py Lines 95 to 96 in 30785b8
|
Whipper offset find needs a (remote) matching AccurateRip entry to perform its task and confirm the drive offset: if none is found, return early to prevent exception. Fixes #208.
I'm still having this issue with latest
Isn't this image built on every new commit ? If not, please push a new build. |
Happening also with a self-built docker image following the README.md from latetst master of today:
|
That image is built from the master branch, which I've decided starting with release v0.7.2 is going to be updated only when new tagged releases are ready to be published.
😉 |
The text was updated successfully, but these errors were encountered: