384
Lemmy (lemmy.world)
submitted 3 years ago by to c/programmerhumor@lemmy.ml
74 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 11 points 3 years ago (25 children)

Is it a lemmy issue or a jerboa issue?

  • permalink
  • fedilink
  • source
  • hideshow 25 child comments
    •
  • [–] 26 points 3 years ago (10 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 17 points 3 years ago (4 children)

    I think it's both, actually. Lemmy is often giving html where json is expected, and Jerboa isn't handling the error well.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 18 points 3 years ago

    🤔 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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 3 years ago (2 children)

    Well, what should Jerboa do? Pretend it received content?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 3 years ago

    If it's Jerboa/Android app issue, why do I get JSON errors using Lemmy on my desktop PC with Firefox? Forgive me if this is a dumb question, I have very little programming knowledge.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 3 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 3 years ago

    lemmy does not return 502 error codes because 502 means "bad gateway" and lemmy is not acting as a gateway, nginx is. An nginx sends the html. All apps should check the status code for codes like this one that don't come from apps.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 0 points 3 years ago (10 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 5 points 3 years ago (5 children)

    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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 6 points 3 years ago (2 children)

    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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -1 points 3 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 6 points 3 years ago

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 0 points 3 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •