Traceback (most recent call last):
File "D:\a\F95Checker\F95Checker\modules\api.py", line 512, in fast_check
File "C:\hostedtoolcache\windows\Python\3.11.2\x64\Lib\json\__init__.py", line 346, in loads
File "C:\hostedtoolcache\windows\Python\3.11.2\x64\Lib\json\decoder.py", line 337, in decode
File "C:\hostedtoolcache\windows\Python\3.11.2\x64\Lib\json\decoder.py", line 355, in raw_decode
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
It also told me to upload file check_broken.bin so here is the content to that.
This looks like the site API is responding with malformed data. I had a couple of errors overnight as well, but working fine for me now. Try reducing the number of Workers and see if you still get error.
This looks like the site API is responding with malformed data. I had a couple of errors overnight as well, but working fine for me now. Try reducing the number of Workers and see if you still get error. View attachment 4197606
I'm using the latest version from the Actions (the release version has a bug where if a full recheck crashes like this to a 429, clicking the recheck button again appears to add the whole queue into the tasks again), and I just used a VPN like Nord to change IPs whenever it wouldn't accept any more requests (sometimes a single IP could go through multiple partial refreshes before I needed to switch IPs)
We've had to impose stricter rate limiting site wide. When multiple user's checks coincide it can effectively cause a DDoS, the most recent downtime 2 days ago was directly attributed to this.
As WhiteVanDaycare suggested, lowering your worker count and minimizing the number of full rechecks should allow you to stay under the rate limiting.
WillyJL, Maybe it's time to start batching full rechecks into 30 game batches with 30 second intervals (maybe set it as a user setting so we can fine tune it in the field)?