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
    link
    fedilink
    arrow-up
    3
    ·
    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
      link
      fedilink
      arrow-up
      2
      ·
      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

  • ciferecaNinjo@fedia.io
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I quit fedia for a while. What brought me back for a moment was the fact that I needed to post a microblog comment in a place that I think is unreachable to Lemmy. Glad to see you’re on top of the problem.

    What’s disturbing about this issue is pics are unimportant anyway. I have images disabled in my browser settings to go lean on bandwidth & yet someone’s cat pic might be standing in the way of text. Once you pin down the exact bugs, I think there’s a high-level bug that hopefully will not be overlooked: if an image fails to be fetched or has a problem of any kind, that should not be a show-stopper for the text content.

    Consider what happens when an HTML-linked pic is unavailable-- the browser shows you a generic icon that indicates an image is expected to be there, but isn’t. Though I realize it’s probably not that trivial in the case at hand if it’s a db query that’s falling over.

    I also have avatar disabled in my profile settings. I wish I could also disable all images in my profile because I don’t want the server to even be looking for images when my browser disables them anyway. From a security standpoint, if fedia suffers a DDoS attack it might be useful to disable images on the server side anyway just because they are so much heavier than text. Well, that’s just something to keep in mind.

  • Canard@fedia.io
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Regarding replies appearing twice, there is/was this problem on Lemmy. So is it a Kbin problem, or just a problem from Lemmy or from a specific client?
    It could be interesting to check for duplicates created from Kbin accounts.