Lemmy is written in rust, that's a java error so the issue lies with the app you're using not Lemmy itself (maybe)
this post was submitted on 04 Jul 2023
275 points (98.2% liked)
Programmer Humor
32396 readers
693 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
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.
Mostly the user count at this point, although things have become more stable the last few hours
load more comments
(1 replies)
Is there a good Lenny app because so far wefwef hasn’t been great for me.
Liftoff is the best I've found so far. Waiting for Sync to come though
Jerboa or just in the browser. Honestly though most people's issues are likely to be because they joined a huge instance which is falling over due to load. Consider making a new account on a smaller instance.
Thunder but features aren't all there
Wefwef has been the best for me so far. I'm a previous Boost for Reddit user, so I'm still waiting for their official Lemmy release and then I'll switch.
load more comments
(11 replies)
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'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.
load more comments
(1 replies)
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.
Actually i was trying to say similar issue
load more comments
(3 replies)
load more comments
(1 replies)
Value of type java.lang.String cannot be converted to JSONObject
Is it a lemmy issue or a jerboa issue?
Serious Answer: This is a Jerboa issue. Lemmy is written in Rust. The error message is a Java error which is what native Android apps use.
I think it's both, actually. Lemmy is often giving html where json is expected, and Jerboa isn't handling the error well.
🤔 The server spits out html when it cannot reach the backend. So one could argue it's a configuration issue because the admin didn't provide enough capacity / didn't set up a proper generic json error for backend failures.
FWIW, Liftoff doesn't handle these super gracefully either.
At any rate I think it's kinda awesome that we get to witness these kinds of infancy problems.
Well, what should Jerboa do? Pretend it received content?
Take it as an error, tell the user about it and then retry with exponential back-off.
It should display a human-readable error message instead of the raw one.
No, it's probably when the app is expecting a json but the server returns an html, which usually happens in case of 502 errors.
No, this is a lemmy issue. The API specification specifies a JSON response, and the server randomly provides HTML, this is a bug in the server. I agree that Jebora should retry in the case of a network failure (timeout, 4xx staus codes...) but it should not have to retry in a case of a server that is not folowing the standard.
load more comments
(1 replies)
I would say Lemmy issue. This is probably a default 502 internal sever error response (which I've been getting repeatedly from lemmy.world). Jerboa (I don't use it btw) is only trying to parse the expected json response. Yes the app could handle the error more gracefully but if Lemmy didn't respond with an error jerboa wouldn't need to.
personally I'd say it's a Jerboa thing. the app should retry loading because sometimes I refresh after this happening and it immediately loads the proper content.
with all the different instances this sort of thing has to be kept in mind
Just retry is usually a bad ideia, specially that this problem is probably an overload, just adding retries can makes the problem.even worse with the app ddosing the server
true
just adding retries can makes the problem.even worse with the app ddosing the server
Twitter has some experience with that
load more comments
(2 replies)
Lemmy realy should not randomly emit errors for no reason, there should be no need for retries in this case. If the specification specifies a JSON response, and the server randomly provides HTML, that is a bug in the server.
The error is not being emitted by Lemmy though. The 502 error message is returned to the client by nginx when the Lemmy server doesn't respond within the a certain time.
Definitely jerboa
I'm having similar errors using liftoff
I'm having similar errors using liftoff
Lmao I got a 504 when trying to open this post
I've seen this on both Jerboa and Connect. And even just now
view more: next ›