Ah, I see. It makes sense that now it is even harder to implement it with the new rate limits. It would probably slow it down considerably if not even crashing it and the cache would be, I guess, considerably higher as well, at least on games that have 10-20 screens. Now, I have no idea how the app is working on these requests, so I might be completely off on this. but in my head, what I said makes sense.
fixed, sam's version api can return "Unknown" at times, previously the checker would ignore if "Unknown" was returned and use the version parsed from the thread. now, this step is performed on my server, and i had forgotten this detail. it was seeing that version api returned *something* and used that as the source of truth. ive fixed the logic, updated the server and cleared the cache for the affected games, you should be able to just refresh.
this im not too sure about.
I don't know bro......is it a problem with F95?Or is it my own problem?
you didnt even read what he said. his message literally says "this is a change from F95 that Willy is working on". you cant even read 11 words, no wonder you skipped reading the explanation in the recent messages.I don't know bro......is it a problem with F95?Or is it my own problem?
yep WhiteVanDaycare it works fine now!a little birdie told me that some pages require 1 post to be viewed, here goes
lol i realize now i was mixed up with the 7 day wait of the old "full recheck". personally im not too fussed if i have to wait 7 days for an update, but thinking about it more, that is a major drawback if the dev releases a bugfix and you dont find out till a week later. thats without even considering users who wouldnt want to wait 7 days!
What I did is basically move the client logic to the server. During a fast check, server will see if 7 days have passed since last time each thread was cached, if so it will cache it again and return a new timestamp to indicate that data changed. As for getting updates in real time despite the 7 day cache timer, it checks the latest updates api every 5 minutes and simply invalidates the cache for newly updated games, so next time someone requests them they are re-cached
What on earth... it's failing to do a dns query for api.github.com... I don't see any reason why GitHub of all things would be blocked by your ISP or OS or antivirus, so I'm guessing it's just you didn't have internet at the time of refreshing. And yeah while handling this error it found a new one, I'll check if this possibility still exists in the code, but please update to newest build, I changed a bunch of stuff and it might be already fixed
Updated to 1229 and i assume this is still the latest one, so far no issues. Now if i think about it, I might have had internet down over night for a couple minutes and app probably did a check at that time. I live in Romania and we have nothing blocked, not on ISP or otherwise, well except the usual region error on YT or other sites.
Aha, you had said that quest failed chapter 2 was blocked, but it's chapter 1. Since I didn't see chapter 2 as blocked, I didn't clear the cache for it. But it was chapter 1 that was blocked, just cleared the cache for it now, you should be all good now if you refresh
What version of the app are you using? The last version that I think is still beta 1229 fixed most of the issues we had. You would need to download it from the action tab on Github tho and it needs an account for that.
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/aiohttp/connector.py", line 1080, in _wrap_create_connection
File "uvloop/loop.pyx", line 2084, in create_connection
File "uvloop/loop.pyx", line 2079, in uvloop.loop.Loop.create_connection
File "uvloop/sslproto.pyx", line 517, in uvloop.loop.SSLProtocol._on_handshake_complete
File "uvloop/sslproto.pyx", line 499, in uvloop.loop.SSLProtocol._do_handshake
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/ssl.py", line 917, in do_handshake
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/Users/runner/work/F95Checker/F95Checker/modules/api.py", line 566, in fast_check
File "/Users/runner/work/F95Checker/F95Checker/modules/api.py", line 213, in fetch
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/contextlib.py", line 210, in __aenter__
File "/Users/runner/work/F95Checker/F95Checker/modules/api.py", line 130, in request
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/aiohttp/client.py", line 1353, in __aenter__
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/aiohttp/client.py", line 657, in _request
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/aiohttp/connector.py", line 564, in connect
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/aiohttp/connector.py", line 975, in _create_connection
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/aiohttp/connector.py", line 1350, in _create_direct_connection
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/aiohttp/connector.py", line 1319, in _create_direct_connection
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/aiohttp/connector.py", line 1082, in _wrap_create_connection
aiohttp.client_exceptions.ClientConnectorCertificateError: Cannot connect to host api.f95checker.dev:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)')]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/runner/work/F95Checker/F95Checker/modules/api.py", line 574, in fast_check
UnboundLocalError: cannot access local variable 'res' where it is not associated with a value
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/runner/work/F95Checker/F95Checker/modules/utils.py", line 87, in coro_wrapper
File "/Users/runner/work/F95Checker/F95Checker/modules/api.py", line 1130, in refresh
File "/Users/runner/work/F95Checker/F95Checker/modules/api.py", line 590, in fast_check
UnboundLocalError: cannot access local variable 'last_changes' where it is not associated with a valueMy server uses Cloudflare self signed certs, so no one would be able to securely connect to it except Cloudflare. And everyone else connects to Cloudflare, and I doubt they have invalid certs being used. So yeah something is probably going wrong either with your system's root CA or python's bundled ones (not sure if it does bundle them tho).
