• csm10495@sh.itjust.works
    22·
    2 years ago

    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
  • shrugal@lemmy.world
    18·
    2 years ago

    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.

  • Rimorso@feddit.it
    2·
    2 years ago

    Lemmy is written in rust, that’s a java error so the issue lies with the app you’re using not Lemmy itself (maybe)

    • Atemu@lemmy.ml
      3·
      2 years ago

      The cause is a 502 from lemmy.

      Jerboa’s handling of that error is also terrible but that’s another issue.