View Single Post
Old 04-27-2021, 10:36 AM   #5846
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 7,005
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
Quote:
Originally Posted by watani View Post
Strictly speaking, no I don't need to use the browser cache. I was just wondering if there was some way to catch that error and proceed to use cloudscraper instead of abruptly quitting the whole update process (i.e. what already happens by default if FFF can't find the new chapter(s) in cache). That way I don't have to completely disable the backup method of reading from Firefox cache. But if it's impossible to implement without replicating it on your end, then it's fine if you leave things as is.
That particular error is happening while FFF is initially reading the cache index. When it fails, the entire cache fails and no pages will be able to be read from the cache.

In that situation, I think it's better to fail entirely.
JimmXinu is offline   Reply With Quote