-
Notifications
You must be signed in to change notification settings - Fork 125
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
Favorites Parser Occasionally Fails with Error InvalidChunkLength #390
Comments
I tried rerunning today, and I didn't see any errors captured in logger. All pages were visited by the script, however 100 doujins were somehow skipped. Not sure if some pages have different html or something to cause the script to not count them anymore. The last time it worked for me was on 2025-02-02 |
My testcase:
Maybe I need to figure out which doujinshi been skipped in |
Here's the HTML I logged. What seems to happen is that even if a page is visited, Cloudflare Error 520 can sometimes popup, resulting in 0 doujins |
I let the above run for a few more pages and it was successful between pages 3 to 6, then same Error 520 popped up for page 7 |
Does error 520 persists at page 7? |
added a global retry option (default 3 times) for fetching favorites at commit 023c896 |
Try version 0.5.24 |
0.5.24 works with no issues! I didn't encounter |
I am using the favorites parser with the options
-F --page-all
. Every now and then, I get the following error for some pages.Connection broken: InvalidChunkLength(got length b'', 0 bytes read)", InvalidChunkLength(got length b'', 0 bytes read)
The number of doujins detected at the beginning
favorites_parser: You have X favorites in Y pages.
will not match with the final results at the endprint_doujinshi: Search Result || Found Z doujinshis
, as I see that the code just logs the error, and then continues iterating through all the pages.Also, even though I get the error above for some pages (say 2 pages), the number of found doujins and found pages will have a difference of more than 2*25, even though the error was logged only twice.
The text was updated successfully, but these errors were encountered: