We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Not really a time stopping bug, and maybe nobody will have an issue with it... but!
I noticed the md5 database can have duplicate entries for the same image, as same md5 and same path.
This happens when because the path gets writtens with / or , depending on where the download is initiated in Grabber.
Basically:
It's only the path column in the db that's affected, the image is properly skipped - as it's recognized.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Not really a time stopping bug, and maybe nobody will have an issue with it... but!
I noticed the md5 database can have duplicate entries for the same image, as same md5 and same path.
This happens when because the path gets writtens with / or , depending on where the download is initiated in Grabber.
Basically:
It's only the path column in the db that's affected, the image is properly skipped - as it's recognized.
The text was updated successfully, but these errors were encountered: