- Dec 21, 2019
- 165
- 179
Update for me went smooth as butter. Had no hangs on quit, no nothing.
Thank you Willy for another quality release.
Thank you Willy for another quality release.
as of 11.0, it should be using SSL certs from your system store. update windows, and also try sfc and DISM (google them)Congrats on 11.0 WillyJL!
I got a weird issue, it's failing to finish the refresh because of the app auto-update rejecting github's SSL cert... Is there a way to disable the app auto update while I'm figuring out if it's an issue local to my computer?
You don't have permission to view the spoiler content. Log in or register now.
DM sentplease send me a zip with the entire contents of your f95checker data folder (should be in app data, check the OP FAQ for exact location), except the images, in direct messages. ill try to understand what went wrong and hopefully recover your data. im assumingsomething wrong with database table migration.
did you by chance go back and forth between multiple versions?
Nodid you by chance go back and forth between multiple versions?
oooh, yeah going into list let me sort by update and then switching back to tiles had it fixed. Thanks! And also thanks for your work on this great tool.Different sorting initially probably due to the new tabs, either disable the independent tab views, or configure sorting again in the list view by clicking the column headers. As for it randomly breaking and having different sorting than what the columns are configured to do, this is a known issue listed in the changelog that I currently have no way to fix, it seems to be a memory corruption in either imgui or pyimgui. Restarting the app or configuring sorting again will fix it
yeah, with all the new traffic the cache api hit the max 600 latest updates requests per hour limit. already hit up Sam and he handled it on their end and will not happen to more threads. im now adding fallback handling for this, then will clear the cache for the few threads that got this error cachedJust got this error while it did an auto refresh. Internet is fine and nothing changed. View attachment 4326230
Ah i see, well I guess is to be expected considering how many use the Checker.yeah, with all the new traffic the cache api hit the max 600 latest updates requests per hour limit. already hit up Sam and he handled it on their end and will not happen to more threads. im now adding fallback handling for this, then will clear the cache for the few threads that got this error cached
yeah. just pushed it, shouldnt happen again as sam added an exception for it, but in case it does its handled a bit more gracefully. also cleared cache for those affected games, should be good now.Ah i see, well I guess is to be expected considering how many use the Checker.
Mint 22 is the latest version. which is based on Ubuntu Noble, which is the latest LTS of ubuntu (release april of this year).I have a hunch that it would work on a newer os version, probably some qt incompatibility. Anyway I'll try to see what's up with that plugin stuff
what great numbering scheme, 2 behind current year, love itMint 22 is the latest version. which is based on Ubuntu Noble, which is the latest LTS of ubuntu (release april of this year).
But yea, it is plausible. let me know if I can do something to help.
Ha. I didn't think about that.what great numbering scheme, 2 behind current year, love it
It looks like whatever is generating the PowerShell script that does the actual update is using the PID for explorer.exe instead of the PID for f95checker.exe for the Wait-Process cmdlet. Which usually won't close until logoff/reboot, hence the hanging update.Microsoft can suck my dick
Always windows being a bitch
this explains it. in the past main.py would re-launch itself to capture log output (capturing log output from python is not possible as what youre usually interested in with logs is what goes wrong in other underlying code like Qt and OpenGL which don't log through python), so the update process would not wait for its own process to exit, but the parent one, because you would have explorer.exe > F95Checker.exe > F95Checker.exe. some time ago i removed this behavior as it was clunky and never worked well, and opted to instead have a debug executable which is suppsoed to run in a terminal to see log output, and now its just explorer.exe > F95Checker.exe. but i had forgotten to change the behavior of the updater. i changed it 1 day prior to releasing 11.0.It looks like whatever is generating the PowerShell script that does the actual update is using the PID for explorer.exe instead of the PID for f95checker.exe for the Wait-Process cmdlet. Which usually won't close until logoff/reboot, hence the hanging update.
I couldn't find a .ps file in the git repo, nor could I readily locate any code that might build that script, so hopefully this is enough to track down the issue.
EDIT: Not sure if it matters, but I'm updating from v11.0 beta 1320
yes, i explained it just 1 message aboveIs this normal? It's been like this since I updated it. Is it because I used the auto update from Beta 1329 to the new v11?You don't have permission to view the spoiler content. Log in or register now.
Ah, I didn't refresh the messages in time my bad. So should I just download a fresh copy of v11 from git?yes, i explained it just 1 message above
Also Startup option, is it in development? cause I want to know how I can setup for it to start with systemMicrosoft can suck my dick
Always windows being a bitch
its already there, has been for years. in the sidebarAlso Startup option, is it in development? cause I want to know how I can setup for it to start with system