Handle OSErrors in a cleaner way

[biggestsonicfan]

Prerequisites

• Did you read FAQ section in readme.md?
• Did you test with the latest releases or commit ?
• Did you search for existing issues in Issues?

Description

For the first time in my history of using PixivUtil2, my Pixiv backup drive ran out of space and all chaos seemed to ensue. For some reason, the logs did not log this information, which I thought was strange, it just printed it out to the console. As I've experienced in the past, when OSErrors are thrown, PixivUtil2 downloads them to the executing directory. So if a 4 MiB image can't be written to the destination, it downloads it to the PixivUtil2 folder... but if there's enough space to update db.sqlite, it does so with the originally intended destination. So the database now has an invalid entry as the file will not be there. I have verified this against all the images that saved to my PixivUtil2 folder (except icon and banner art), and only 1 image saved as the filename itself, ignoring the config.ini for some reason.

If you're running a batch file, or have stepped away from PixivUtil2 to play a game or surf the net, I don't think OSErrors should just be allowed to continue. I think these exceptions should be handled like KeyboardInterrupt, where it prompts if you want to continue. If you get an "Invalid Argument" or "No space left on device" error, chances are it's not going to fix itself during the entire download queue you have left. PixivUtil2 should halt and allow the user to attempt to take care of the problem before continuing, or be allowed to abort then and there. No one wants to wade through a PixivUtil2 folder with hundreds or thousands of images in it, I'm sure.

UPDATE EDIT: Okay, apparently I thought all the images in the PixivUtil2 folder didn't make it to the destination path, but I was wrong. Those images were downloaded regardless that they existed in the destination path. I don't know why this is.

Steps to Reproduce

This will be left as an exercise to whomever wants to attempt to tackle this. My suggestion would be to use VirtualBox and add a very small created drive, maybe 20 megabytes, an set that to the PixivUtil2's destination.