-
Notifications
You must be signed in to change notification settings - Fork 66
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
Verify license acquisition succeeded #4
Comments
See also #30 — still an issue. Failure at this stage should display clear instructions on how to resolve the issue, which AFAICT simply consists of trashing the original ODM along with any derivative files generated so far, and retrying with a freshly downloaded ODM. |
This is still an issue and I would agree that instructions on how to resolve this (delete / redownload) would be appreciated. |
Btw. 25a3e94 is intended to address this. |
...also ab1dfcc. Ideally, Closing this since 25a3e94 and ab1dfcc should now make recovery easier, but if anyone stumbles on this in the future, feel free to open a new issue. |
Either by checking the file contents or the result of the curl call in
acquire_license
.(Debugging upstream errors requires a tedious extra step if the license fails; see #3)
The text was updated successfully, but these errors were encountered: