More robust error handling

Question

More robust error handling

wojtekpolska opened this issue 3 years ago · 8 comments

wojtekpolska commented 3 years ago

then after pressing enter it says loading, but it loads the wrong version (1.1.3 instead of 1.1.4)

(i downloaded 1.1.4 from github)

and it never loads

I redownloaded it MULTIPLE TIMES and im 100% sure i clicked the 1.1.4 version link

Answer 1 · 2021-07-16T20:32:07.000Z

You can try just ignoring the error. As for the version, apparently it wasn't updated in the app; just ignore it as it should be 1.1.4.

Answer 2 · 2021-07-16T20:33:59.000Z

but it doesn't load at all

it stays like that saying "Loading"

EDIT: After few restarts it finally loaded

Answer 3 · 2021-07-16T20:36:36.000Z

How and where are you running the exe?

Answer 4 · 2021-07-16T20:37:38.000Z

double-clicking on it

but it seems to start working now every time i open it

Answer 5 · 2021-07-16T21:16:17.000Z

@TheShadowEevee there are other problems tho
if i keep it opened for too long this happens:

Answer 6 · 2021-07-16T21:23:52.000Z

Please try closing the program, removing the cache directory and then making sure that your discord client is running.

In your discord settings, unlink/remove the application's access to your discord account.

Finally, re-run the exe. That should force the program to run through the authentication flow again, hopefully solving your issues.

EDIT: Please send me your discord user ID so I can check your riitag for errors

Answer 7 · 2021-07-16T21:56:32.000Z

my discord id is wojtekpolska#5541

Answer 8 · 2021-07-16T22:31:23.000Z

Okay, so I think I found the issue.

"new_riitag" is None when this error occurs, but because the value of that var is set to be equal to "self._last_riitag" and that statement does not get executed when "self._last_riitag" is None, the only way for "new_riitag" to be None is for the "fetch_user" method on the user object to return none when it's time to do a new riitag check. This method returns None if and only if an HTTPError occurs, which means that this is a case of the server failing and the program not handling it properly.

I looked into a couple of sentry reports about this same error and sure enough:

GET http://tag.rc24.xyz/<user id here>/json [502]

{reason: Bad Gateway}

I can't fix the issue on the server side, but I can make the program more resistant to VPS shenanigans. Not sure when I'll get to actually fixing this though, don't expect too much of it. In the meantime, you can just ignore the error and/or restart the program when it happens.