this post was submitted on 04 Jul 2023
289 points (98.0% liked)
Programmer Humor
32559 readers
288 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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
Twitter has some experience with that
true
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.
When you get a 502 error, that's not coming from lemmy, it's coming from nginx. If you're saying that nginx should send any error data along with the status in json if the accept headers require it, that's a task for nginx but it wouldn't happen in this case anyway since the json wouldn't be what they were expecting anyway. The app should be handling non success responses better is the point being made here.
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.
[This comment has been deleted by an automated system]
Yeah this makes more sense than my original comment