Skip to content
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

Solution for "Could not load file in library: Blogs\Index\BLOGNAME_files.tumblr" #546

Open
ErikBrown2 opened this issue Jun 9, 2024 · 1 comment

Comments

@ErikBrown2
Copy link

Is your feature request related to a problem? Please describe.

Every now and then I see the error message "Could not load file in library: Blogs\Index\BLOGNAME_files.tumblr"
I am not sure but I have the idea that it might be caused by me unintentionally starting two instances of TumblThree.
My PC is very slow and sometimes it appears that TumblThree is not starting after I clicked on the program icon. So I click again on it. Only to see later that I have two instances of TumblThree running.

Describe the solution you'd like

Due to this I would like to suggest two program changes:

  1. Add a setting option that, when ticked, ensures that only one instance of TumblThree will run at any time.

  2. To recover from this error, the user needs to manually delete the index file of the blog. For a not so computer savvy user this might be a bit difficult to do. So I would like to suggest that when this error is detected at the start of the application, that a pop up will be shown to the user which asks the user if the corrupted index file should be deleted. This way any user can easily recover from this error.

Then the question comes up if TumblThree will download all files again for the affected blog if the index file is deleted and the blog is added again. Or will it detect that the files already exist? Of course it would be preferred that TumblThree will not download the existing files again.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@thomas694
Copy link
Contributor

If the index file file is deleted, the files are downloaded again except they have been already downloaded in another blog and the global check is enabled.

A manual workaround (to rebuild the index file without downloading again):

  • Disable LoadAllDatabases in Settings.json (while app closed) or in dialog ("Check for file existence globally...")
  • Add the blog again or use old blog file, if you only deleted "blog_files.tumblr"
  • Enable CheckDirectoryForFiles in blog file (while app closed)
  • Start app and scan the blog, or force scan if you reused blog file
  • Don't forget to disable CheckDirectoryForFiles afterwards (and enable LoadAllDatabases if you use it)

thomas694 added a commit that referenced this issue Aug 9, 2024
- If multiple instances with same download location are run, unpredictable things (e.g. blog file corruptions) can happen.
- In each main download location a running.lock file is hold during execution. So it's OK to run multiple portable versions with different download locations, but not multiple times the normal version.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants