Tool Others F95Checker [WillyJL]

[gguigui]

Indeed, that was the issue, NextDNS was blocking the address.
Thanks!

Did you enable any option in the proxy section of the settings? If so, might be you entered the proxy settings wrong. If not, might be a third party involved in your connection setup blocking access to my api for some reason. Maybe an antivirus blocking connections to new domains with no prior reputation, or same from the internet provider. Or could just be the antivirus blocking the app from accessing the internet at all. Try disabling antivirus, changing DNS settings to use cloudflare's 1.1.1.1 or try on another network.

 

[ivanfneunfünf]

Fuck the full check is crazy fast now. love it

 

[WillyJL]

WillyJL

I managed to reproduce crash the second, third, and fourth time

i see, nothing makes it particularly obvious what the issue would be. only thing i can think of is that the memory corruption that causes the sorting issues to begin with just happens to corrupt another piece of memory on your system, which leads the process to a panic as it does not know what to do with the overwritten bad memory.
as a sidenote, im wondering if maybe this memory corruption is somehow related to the "independent views" setting. maybe imgui is has a bug keeping track of the separate tables, idk. ill have to do more testing.
maybe try looking in windows event viewer or something like that. when processes crash there should be a record of it somewhere in windows, but im not a windows guy so idk where. a crash dump would be best but idk if windows does those, even just knowing what the crash is (like segmentation fault or bad access) could help.

 

[WillyJL]

Is there a way to manually fix release dates?
Some new releases don't have the proper date written on the first post of a game.

Some kind of check if the update is just received by F95Checker, but the release date is like 6 months before, so it would treat the day it received the update as the release date.

writing to mods all the time that they should fix the Game updated field is not always feasible.

ive noticed some weird things happening last few days, 2 games i had tracked got the last updated date changed without an update (games that have been completed/abandoned for years), so they showed up at the top of my list. i noticed that the mod had changed the "thread updated" value, but not the "release date" value. i assume that usually the "thread updated" value is changed when the thread is updated with a new game update, not for smaller edits to OP, but apparently some mods change the date anyway. i have changed the cache api to prefer using "release date" instead of "thread updated" from the OP. all games will slowly be parsed with this change over the next week as the cache expires, let me know if this produces unexpected results. it was using "thread updated" because that sounded like it means game updates, while "release date" sounded like when the game originally released, and i dont see a specific guideline about this in f95zone game posting rules/template, but from what i can see usually "release date" refers to when a certain update that is posted to f95zone was originally published by the author, not when the game as a whole was originally released. so i think that this behavior is acceptable, and will prevent "fake updates" from showing up when mods edit the thread updated date without an update.
as for the issue you mentioned here, where the mods dont update these dates at all, idk if anything can be done about that.

EDIT: although, i just realized that it could also happen that a game is updated but the update is not published to f95zone until months later, and this change would mean the udpated date shows as long ago even though you get the notification now... idk what the best solution is then. ill keep this change for now and see what people think

 

[Versace217]

Thanks for all your work WillyJL !

I downloaded the beta version since 10.2 couldn't handle that many thread requests. I had a question though; will you be eventually adding an auto-update option for the F95checker client itself? For both public and beta releases.

 

[ascsd]

Thanks for all your work WillyJL !

I downloaded the beta version since 10.2 couldn't handle that many thread requests. I had a question though; will you be eventually adding an auto-update option for the F95checker client itself? For both public and beta releases.

auto-update for public release is already a thing
beta most likely will not as it requires github account

 

[WillyJL]

auto-update for public release is already a thing
beta most likely will not as it requires github account

I'm considering adopting a system similar to what I use for flipper stuff however. Since with the cache api I now have a server dedicated to this project, I could easily also host a update indexer on it, which will serve a json of the latest versions, and gets built binaries sent to it by GitHub actions. Would make it trivial to have a beta update channel. But that's for after 11.0 release

 

[WhiteVanDaycare]

Not sure what is going on here, but your caching server picked up the version change but not the Last Updated change:

Not just this game, but a few of them that I noticed.

 

[WillyJL]

Not sure what is going on here, but your caching server picked up the version change but not the Last Updated change:
View attachment 4309126
Not just this game, but a few of them that I noticed.

ive noticed some weird things happening last few days, 2 games i had tracked got the last updated date changed without an update (games that have been completed/abandoned for years), so they showed up at the top of my list. i noticed that the mod had changed the "thread updated" value, but not the "release date" value. i assume that usually the "thread updated" value is changed when the thread is updated with a new game update, not for smaller edits to OP, but apparently some mods change the date anyway. i have changed the cache api to prefer using "release date" instead of "thread updated" from the OP. all games will slowly be parsed with this change over the next week as the cache expires, let me know if this produces unexpected results. it was using "thread updated" because that sounded like it means game updates, while "release date" sounded like when the game originally released, and i dont see a specific guideline about this in f95zone game posting rules/template, but from what i can see usually "release date" refers to when a certain update that is posted to f95zone was originally published by the author, not when the game as a whole was originally released. so i think that this behavior is acceptable, and will prevent "fake updates" from showing up when mods edit the thread updated date without an update.
as for the issue you mentioned here, where the mods dont update these dates at all, idk if anything can be done about that.

EDIT: although, i just realized that it could also happen that a game is updated but the update is not published to f95zone until months later, and this change would mean the udpated date shows as long ago even though you get the notification now... idk what the best solution is then. ill keep this change for now and see what people think

 

[WhiteVanDaycare]

But as you can see, the Last Updated date was changed on F95 but not in your cache. These were new versions, it picked up the new version number.

EDIT: so the opposite of what you described, although that is super annoying as well tbh

Then there is this one that will be on the top of the Last Updated list for quite awhile due to someone fat fingering the date.

 

[WillyJL]

But as you can see, the Last Updated date was changed on F95 but not in your cache. These were new versions, it picked up the new version number.

well nothing i can do about that, the mod published the update and changed the date after. the api cached the new data, but the date was changed after. only place i can reliably get a last updated date is by fetching the whole thread, and this is not possible to do all the time. it monitors latest updates to detect other changes quicker, but that does not give a date or a time, it gives how long ago in human readable form, which i cant use either and it horribly rounded.

Then there is this one that will be on the top of the Last Updated list for quite awhile due to someone fat fingering the date.

tell them to fix it then
and clearly theres something very wrong there anyway, because latest updates shows this one as updated 5 years ago. its not an issue on my end, something is going very wrong with that thread overall.


unfortunately we rely on humans here, and humans cannot be relied on, so have to make do ¯\_(ツ)_/¯

EDIT: i asked sam if it would be possible to include an actual timestamp in latest updates, rather than just "1 day" ago. if that happens, ill change it to use this date when possible, otherwise fallback to "thread updated" or "release date" from thread if theyre detected, otherwise use the last time OP was edited.
for now i reverted it to how it was before, prefer "thread updated" before "release date", but still wouldnt fix the first issue you encountered, which (i assume) is a mod publishing an update before editing the date in OP. if we get a proper timestamp in latest updates, that shouldnt be an issue anymore

 

[ascsd]

I'm considering adopting a system similar to what I use for flipper stuff however. Since with the cache api I now have a server dedicated to this project, I could easily also host a update indexer on it, which will serve a json of the latest versions, and gets built binaries sent to it by GitHub actions. Would make it trivial to have a beta update channel. But that's for after 11.0 release

yea, thought about ways to do it, but is it worth it for beta?
theres the risk everyone on beta updates to a buggy release that breaks their db then good luck dealing with the fallout

one benefit would be so that everyone who is ok taking the risk will be on the latest so they can be your "beta testers", easier than asking them to manually update

 

[WhiteVanDaycare]

yea, thought about ways to do it, but is it worth it for beta?
theres the risk everyone on beta updates to a buggy release that breaks their db then good luck dealing with the fallout

one benefit would be so that everyone who is ok taking the risk will be on the latest so they can be your "beta testers", easier than asking them to manually update

Agreed, auto update would be best just for stable version. But if you do move forward with auto-update of beta versions can you have it back up the database and add a setting to turn off auto update?

 

[WillyJL]

yea, thought about ways to do it, but is it worth it for beta?
theres the risk everyone on beta updates to a buggy release that breaks their db then good luck dealing with the fallout

one benefit would be so that everyone who is ok taking the risk will be on the latest so they can be your "beta testers", easier than asking them to manually update

yeah thats true, but i think ive started to have a better development cycle lately. i dont push to main unless ive tested it myself and im confident it wont atleast cause irreparable issues. that work in progress stuff is reserved for separate branches, which i didnt use much in the past but started really using lately on other projects and now here too. its a bit weird making pull requests to my own project but it means that its a more sane development cycle and stops me from merging something stupid as i re-read everything before merging.

and yeah for sure, having those who want to use beta always on the latest beta saves me from saying that bugs are already fixed and so on.

 

[WillyJL]

Agreed, auto update would be best just for stable version. But if you do move forward with auto-update of beta versions can you have it back up the database and add a setting to turn off auto update?

i disagree. its not an auto update, it checks for updates and asks you if you want to update. nothing is automatic without your approval. and yeah, a db backup system would make sense, could trigger one right before starting the update. wouldnt even need to be restricted to updates, could haev a button in the sidebar settings.

 

[ascsd]

haha yea i'm in the same boat with branches. Feels weird when you're the only contributor, but after seeing the benefits at work and also being burnt myself with my personal projects, just pushing multiple changes directly to main in 1 commit then having to revert things line by line (even worse when its multiple changes done to 1 line ) single-purpose PRs and branches have saved my ass

db backup system would solve majority of the problems like WhiteVanDaycare suggested

the only other thing I can think of is if there is a deliberate risky or breaking/backwards-incompatible change. theres a small benefit of having a way to mark a beta release as not eligible for auto update, but the use-case for that might never arise

 

[KaosKally]

never seen this error before
Now i realized i am a few versions behind...

 

[forgetmaster]

429 - Too Many Requests . That’s an error.

Client issued too many requests. That’s all we know.

This is what I getting in the broken.html fil.
I have added 1200 games in the checker.
but all was working fine till like 1100.

 

[WillyJL]

429 - Too Many Requests . That’s an error.

Client issued too many requests. That’s all we know.

This is what I getting in the broken.html fil.
I have added 1200 games in the checker.
but all was working fine till like 1100.

That's the only thing we've been talking about for the last month. Update to the beta.

 

[WillyJL]

never seen this error before View attachment 4314492
Now i realized i am a few versions behind...

It will inevitably happen every now and then. When the cache api has some problem caching data for a game it saves this error and schedules a retry (how soon the retry is depends on the kind of error). This one just means that cache api was unable to reach f95zone to get the game info, either due to temporary downtime or server overload. This kind of error is retried after 15 minutes. I plan to eventually have a better explanation and error message, but for now all errors returned directly by the cache api use that kind of popup. (Only exception is the error for threads being deleted, which still asks you if you want to convert to custom game or whatever)