View Single Post
Old 04-16-2022, 07:03 PM   #7020
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: 6,993
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
New Test Version Posted

2022-04-16
- Apply connect_timeout setting to network requests.

In Jan 2021, I re-did FFF's networking code to make it more modular and better allow for the Browser cache and Proxy shenanigans we find ourselves needing.

Along the way, I apparently forgot to actually use the connect_timeout setting in the new code. Without a timeout setting, the underlying network code just doesn't timeout. Ever.

This test version uses the old default setting of 60.0 seconds. (A setting of 4 retries is hard coded and not configurable.)

If you frequently hibernate during downloads, you might experiment with a shorter connect_timeout setting.

Depending on a number of factors, you may get reported errors instead of a clean resume, but it shouldn't just hang forever on connections now. I would also set continue_on_chapter_error:true under [defaults] if I were you.
JimmXinu is online now   Reply With Quote