Tool Others F95Checker [WillyJL]

[noty2]

Keep getting an error on game checking same as the ones above me, error 429

 

[Bruh333!]

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 tried your suggestion but it still threw up the same error unfortunately

 

[Blither]

i tried your suggestion but it still threw up the same error unfortunately

Same issue here

 

[WhiteVanDaycare]

Yeah, I'm getting the same error now as well. I think it's related to the F95 API.

Explanation of error -

You must be registered to see the links

 

[GrammerCop]

Well, I hope it gets fixed soon. I have a full recheck of about 1000 games coming up.

 

[Nerro]

Yes hoping for a fix soon also. Im so dependent on this program It only scans 20-30 games before giving an error, then I have to restart the app.

 

[ipaqi]

Well, I hope it gets fixed soon. I have a full recheck of about 1000 games coming up.

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)

 

[GrammerCop]

It happened to me. I cleared my cache and it worked...for now. Thanks to WhiteVanDaycare for that explanation link.

 

[miglosch]

macOS login problem...

every time I try to use this app, I get a blank login window (see attachment)

any suggestions?

 

[Bruh333!]

It happened to me. I cleared my cache and it worked...for now. Thanks to WhiteVanDaycare for that explanation link.

i cleared cache and im still getting the error.

 

[Madanach]

+1 to all the problems mentioned above. Seems to be related to some change in the API.

 

[Sam]

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.

 

[Nerro]

Even reducing workers from 20 to 5 I still get this after like 20-30 rechecks.

 

[evilution382]

even with 1 worker the issue persists
I understand why they had to make the change, it sucks though

 

[Bruh333!]

even with 1 worker the issue persists
I understand why they had to make the change, it sucks though

me too i tried 1 worker and i could only get through like 20 rechecks before it threw up the same error of thread parsing like Nerro

 

[GrammerCop]

Is this going to kill the app (render it useless)? WillyJL
Would be a shame.

 

[ipaqi]

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)?

 

[WhiteVanDaycare]

Or F95 could use a caching server for their API. It does cost money (which sucks) but prevents API requests from impacting the main servers.

Sam is this something you guys have had a chance to consider yet?

 

[Sam]

Or F95 could use a caching server for their API. It does cost money (which sucks) but prevents API requests from impacting the main servers.

Sam is this something you guys have had a chance to consider yet?

The quick checks aren't a problem as they're hitting a cached API.

It's the 'full' checks that are the problem, as they make requests to Xenforo.

The solution would be to space out the requests more, and to sleep when a 429 is encountered then retry.

 

[blackop]

I'm actually having 429 errors even with implemented 1 RPM limit and 1 worker. Not so sure anymore if it's per-user/IP limit or API gateway is being overloaded.