-
Notifications
You must be signed in to change notification settings - Fork 15
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
Not resuming images downloading after errored out #15
Comments
Problems resuming past dumps are unfortunately a little bit of a known issue (though we thought we had fixed it). The main workaround at this point would probably be re-running the dump from the start with the parameter In the meantime, apologies for the inconvenience, and thank you for bringing this to our attention! |
no worries! I just decided to bring it up in case it signals some other underlying issues. |
I changed the default delay from |
--- - Introduce `sha1File` - save more metadata(`size`, `sha1`) into `images.txt` - feat: better file dump: - validate image's size and sha1 - show progress - better resume > Improved the resume mechanism. (fix: #15) First check whether the `file` and `file.desc` exist, and then check whether the `size` and `sha1` of the file correspond to `images.txt`. If any check fails, the file and the .desc of the file will be downloaded again. If all pass, the download of this file is skipped. You can even delete random pictures and .desc files and try to resume again. - pre-work for incremental image dump - remove `start` param from `generatorImageDump()` > the images resume mechanism has changed. we don't need `start` for resuming anymore. - other minor improvements
I am trying to create a dump for a Fandom wiki. The download errored out after a while. When I attempt to resume the downloading, the script downloads the images from the beginning, saying no image dump was found.
Error:
Resuming with:
Gives
The images from the session does exist in folder.

The text was updated successfully, but these errors were encountered: