While I’m skeptical there are many people still using fedia.io, I have been continue to try to fix the error 500 problems. These errors are caused by kbin thinking it stored database records with pointers to images (like the avatar image, images attached to posts and the like) but not actually finishing. So when certain records are pulled up (magazines or posts or users) where there is a missing image record, an error 500 exists. I’ve continued to find more instances of this and frankly I don’t know what is causing the problem. As a mitigation, I have been running cron jobs every 15 minutes to correct these broken links. This morning, I believe I chased down the cause of the last remaining disconnect and have that being fixed as well.

I suspect there are still other problems, like replies appearing twice. I will try to figure out what is going on with those as I can.

  • e569668@fedia.io
    0·
    1 year ago

    I feel like I’ve been saying this for a while now but I’m hopeful full release will happen soon and that will hopefully make it easier to chase down bugs, at least different sites might be versioned so we get an idea of when problems manifest.

    Just as an FYI there’s a pretty bad bug right now https://codeberg.org/Kbin/kbin-core/issues/1019 that makes kbin.social users unable to see text and image posts to kbin.social if they have domains blocked. It seems to only be affecting kbin.social so I can’t say for sure if it’s in the develop branch or something specific to the setup ernest has. I’ve been basing my guesses off things like localization versions and, based on that, kbin.social is actually behind in commits compared to other kbins, so that makes me wonder if it’s not something in the develop branch, but I could be mistaken, just a heads-up something to watch out for before updating in case of risks (at least there’s a way to mitigate it, but as far as I can see it isn’t happening on fedia.io)

    • e569668@fedia.io
      0·
      1 year ago

      Regarding image thumbnails, it is quite a mess :( There must be some bugs happening somewhere with the pipeline for caching, and they started being mixed up on kbin.social as well which is worrying

      For instance, look at this user https://fedia.io/u/@Facelikeapotato@lemmy.ml almost all of their thumbnails are wrong. Really you can browse https://fedia.io/m/cat@lemmy.world and just look for non-cat pictures. I’ve seen all kinds like nsfw, git repos, news thumbnails, but here are some examples [1] [2] [3].

      I posted a theory here https://fedia.io/m/kbinMeta@kbin.social/t/221067/-/comment/1196287 when I noticed that: it seems to happen a lot on instances that go down often or don’t respond quickly, so my guess was it’s having trouble getting a response, and then it just fails and, potentially, uses the next thumbnail value it gets. That’s based off of the thumbnails for nearby entries being similar, as I posted in that comment the one that was wrong was using the same image as a post 31 seconds after it was made

      As I posted here https://fedia.io/m/fedia/p/66268 I notice it’s easier to browse with show thumbnails turned off, as that stops the 500s when the image thumbnail has issues. Sadly it still happens on some pages and I ~think that’s because avatars for users, which are also cached, are shown on that page, like the notifications page, and there is no way to disable displaying user avatars on those pages

      • jerry@fedia.ioOPM
        0·
        1 year ago

        Thanks. Are you still seeing 500s even now? If so, can you point them out to me?

        • e569668@fedia.io
          0·
          1 year ago

          my profile, as well as hitstuns apparently - https://fedia.io/u/e569668 https://fedia.io/u/hitstun
          my microblog sub feed - https://fedia.io/sub/microblog … that doesn’t help you I guess lol, let’s see it appears to be https://fedia.io/m/kbin@kbin.social/microblog and https://fedia.io/m/FloatingIsFun/microblog for me

          Definitely can confirm posts that were 500ing for me yesterday are working now though, so thank you for taking the time to fix things up

          • all-knight-party@fedia.io
            2·
            1 year ago

            Just curious, are you still getting 500s? I left Fedia temporarily because the 500s just got unusably bad, but I’ve noticed I can view my profile and subscriptions without issues now, and the instance I moved to seems like their owner disappeared off the face of the earth, so I’m considering returning, but don’t want to run into 500s anymore.

            • e569668@fedia.io
              1·
              1 year ago

              So my profile as you can see still 500s. There’s also the duplicate thread / comments issue which persists.

              jerry just updated to latest yesterday, so fedia now has a lot of the new changes which should hopefully make it a little more stable, though there was a big effort to fix a lot of the 500s riiiiggghhhhtttt as he updated so I’m not sure if he snuck in the middle of those updates or caught them all. Some times I might get a 500 looking at my sub list, but it will fix itself later. I assume jerry is still running scripts which basically try to resolve those issues on a cron job so it might not work for a bit but then work later.