Lemmy is written in rust, that’s a java error so the issue lies with the app you’re using not Lemmy itself (maybe)
The cause is a 502 from lemmy.
Jerboa’s handling of that error is also terrible but that’s another issue.
Memmy doesn’t do well with it either.
Of course it doesn’t bode well for the instance itself that it’s throwing so many…but it’s unclear if that’s an operator problem or a code base problem.
It could also just be a server load issue.
Lemmy.world, the community the instance is hosted on, has been having a few issues between the 0.18.1 update, and the amount of users on the platform.
Is there a good Lenny app because so far wefwef hasn’t been great for me.
I’m using it on iOS and don’t get me wrong the app looks beautiful. I’m finding issues with communities not loading posts, comments or general sync issues. I have an issue where trying to reply to a comment would overlay the comments over the textfield.
I am using Memmy at the moment and it’s well decent
I’ve seen this more times than my own family
Afaik this is not an error from Lemmy but from nginx, which is not able to relay the request to Lemmy and therefore returns a 502 bad gateway response. Imo this just means the servers are over capacity, so most likely a scaling/infrastructure issue.
I had a quick read of the code and it looks pretty solid to me. Not the most “enterprise” code imaginable, but definitely no code smell or quick hacking job.
You know at least it printed an error. I hate when things silently swallow errors.
I’m looking at you, Python programmers:
try:
<100 lines of nonsense>
except:
pass
We are not savages now we use
with suppress(Exception):
> 100 lines nonsense
I am in the process of fixing a bug at work where pretty much every method has a try(Exception e){…}catch{LOGGER.error(…)}. The method calling my team’s method needs to know when an interrupted exception is thrown. So far I have fixed this in 10 different methods, and we keep finding more. It’s like playing whack-a-mole.
that’s Jerboa issue but probably because It received something from the server that it shouldn’t
No, the server gave a 502 instead of a JSON and Jerboa doesn’t handle that gracefully.
Seems like the 4 apps I use all have the same issue though which makes me wonder if it’s something in Lemmy causing the issue (not the apps).
