Nah I don't use fancy zones. I think i did previously in the past but it's not currently installed since I don't really have any use for it anymore the win11 stuff is good enough for me. My dos box just reopens wherever I closed it off before which is typical behavior so.
that can be fixed in the settings.
It’s working perfectly as instended. All those games are installed. Only that some of them are not on the latest version. The new tool betas, and the new upcoming update, will show it more clearly with a triple state checkbox for not installed, installed but outdated, and installed on latest version
If this is your intention it is definitely not clear. Will be glad to see the next update then.
on the current version it is not super clear, but you can still tell why. if a game was marked as installed, then an update comes, it is still installed, but not on the latest version. so the checkbox was off to allow you to mark it as installed on latest version, but technically it still counts as installed. you can tell that by the version text: it shows both the installed version number and the latest version number, with appropriate icons to distinguish them. the installed filter has an option you can use to include or exclude the outdated installs. new beta and next update will keep this behavior, but make it more clear. instead of being on or off, the checkbox will have a third state for installed but not on latest version, and there will be an update marker icon to make it as clear as day what is happening. you can have a preview here
I understand your logic, but as a software engineer I would say it is flawed. We'll just agree to disagree and I'll wait for the next release. Thank you!
Yea I know it’s still an issue, but really I don’t have many ideas and haven’t looked into it properly yet. The only detail I can think of is that maybe it’s is something Debian based related, because yohudood also reported the same issue and they were on pop os, while I remember you saying that you’re on devuan (both Debian based in some way)... and I haven’t had issues on either arch Linux or Garuda Linux (which is arch basedJust as an info for WillyJL : I still get my error with the 9.4 release, only the first 5 line-numbers are a bit different.
hope it helps somehowYou don't have permission to view the spoiler content. Log in or register now.
EDIT: Forgot to mention, that imgui.ini file mentioned in gui.py was never created, not even with other 9.x release versions.
The fact that it started happening recently, happens consistently, at about the same refresh percentage, and that is towards the end of the refresh, suggests to me that it may be some new game you added recently. If you want play around with it a bit, or send your db.sqlite3 in my dms
Traceback (most recent call last):
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\connector.py", line 980, in _wrap_create_connection
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\asyncio\base_events.py", line 1067, in create_connection
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\asyncio\base_events.py", line 1052, in create_connection
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\asyncio\base_events.py", line 963, in _connect_sock
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\asyncio\proactor_events.py", line 705, in sock_connect
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\asyncio\windows_events.py", line 817, in _poll
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\asyncio\windows_events.py", line 604, in finish_connect
OSError: [WinError 121] Le délai de temporisation de sémaphore a expiré
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "D:\a\F95Checker\F95Checker\modules\api.py", line 809, in refresh
File "D:\a\F95Checker\F95Checker\modules\api.py", line 789, in worker
File "D:\a\F95Checker\F95Checker\modules\api.py", line 294, in check
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\client.py", line 1141, in __aenter__
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\client.py", line 536, in _request
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\connector.py", line 540, in connect
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\connector.py", line 901, in _create_connection
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\connector.py", line 1206, in _create_direct_connection
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\connector.py", line 1175, in _create_direct_connection
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\connector.py", line 988, in _wrap_create_connection
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host f95zone.to:443 ssl:False [Le délai de temporisation de sémaphore a expiré]
I'm on Win11 and getting similar logs from the same issue it seems.. if that helps.
Traceback (most recent call last):
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\connector.py", line 980, in _wrap_create_connection
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\asyncio\base_events.py", line 1067, in create_connection
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\asyncio\base_events.py", line 1052, in create_connection
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\asyncio\base_events.py", line 963, in _connect_sock
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\asyncio\proactor_events.py", line 705, in sock_connect
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\asyncio\windows_events.py", line 817, in _poll
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\asyncio\windows_events.py", line 604, in finish_connect
OSError: [WinError 121] The semaphore timeout period has expired
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "D:\a\F95Checker\F95Checker\src\modules\api.py", line 811, in refresh
File "D:\a\F95Checker\F95Checker\src\modules\api.py", line 791, in worker
File "D:\a\F95Checker\F95Checker\src\modules\api.py", line 296, in check
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\client.py", line 1141, in __aenter__
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\client.py", line 536, in _request
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\connector.py", line 540, in connect
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\connector.py", line 901, in _create_connection
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\connector.py", line 1206, in _create_direct_connection
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\connector.py", line 1175, in _create_direct_connection
File "C:\hostedtoolcache\windows\Python\3.10.8\x64\lib\site-packages\aiohttp\connector.py", line 988, in _wrap_create_connection
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host f95zone.to:443 ssl:False [The semaphore timeout period has expired]very different error to what you were replying to, completely unrelated in fact, but it is the same error that ＧＡＢ also reported and that someone put on github. im looking into it but im not really sure... looks like a normal timeout error, but deeper down in windows hell... in fact im not having this issue on linux...
hm perhaps i should make a FAQ note about it, just never occurred to me. if you wish to of course you can run from source and pull any commits i make, but i cant guarantee any stability that way. the builds are just like the binary releases, just that i can trigger them when i want so they might be unstable, but still if i trigger a beta build its because either i made some significant changes that i feel like are in a decent usable state and just need testing, or i am trying to fix some other error (building and bundling binaries actually leads to very different behavior from source execution so it can be a pain, just look at the commit messages from when i was trying to fix macos builds (they are still broken)). either way for the beta builds (and also full releases) i use github actions, so just head to the actions tab, find the last run that wasnt skipped (either a green tick mark or a red cross). there you will find build artifacts for the 4 platforms (3 + source). if the build was marked as failed, then it doesnt mean that its fully failed. it mightve failed for one platform but others might still be available, so dont let a red cross icon scare you. beta builds will check for updates (unless that specific beta build had trhe auto update system broken for some change i made), in the sense that it will not auto update back to the previous stable release, it will not update to new betas, but when a newer stable release is out it will prompt you, so if you see some interesting feature in beta, go ahead and use that, then it will update when stable release is out
I actually wandered there before and I see the artifacts and their size, but no way to download them.
Thanks for the reply. I'm getting ready for work at the moment, but I will tinker with it when I get home. I love your app by the way. It makes life so much easier.