We recently updated to 0.18.0 and I haven’t really had a chance to fully test it. I took a snapshot before the upgrade, so we have a working state to roll back to if need be.

Please do not hesitate to post here. Rolling back snapshots will cause us to lose new posts that took place after I took the snapshot.

  • twenty_onesided_die@burggit.moe
    5·
    1 year ago

    Don’t know if it’s a new issue (or if it’s not an issue at all) but upvoting pops out the up-arrow and the number of upvotes and pops in a “loading sign”. That moves the ui a bit to the left (save, view source, more, buttons)

  • Pink Bow@burggit.moe
    3·
    1 year ago

    Continuing to get seemingly random orange toasts popping up. I think the latest one I got while typing in a comment said something about JSON but I didn’t screenshot it in time. It didn’t seem to actually matter, though (Firefox 114 on Linux). Assuming these are all upstream as well.

    EDIT: Got it again. Here’s a screenshot:

    • Burger@burggit.moeOPM
      1·
      1 year ago

      That very well could be. Do you notice the site running slow too? Thinking it’s just me since nobody else complained about it.

      • Nazrin@burggit.moe
        3·
        1 year ago

        I saw it running slow on some images, but then realized the image was a 4k image. I have had orange json toast before, and it led to a few seconds of the /error page

        • Burger@burggit.moeOPM
          2·
          1 year ago

          Yeah, that’s the sucky part about hosting your stuff internationally. Latency and throughput are severely diminished at certain times because of the vast amount of hops packets have to route through. I’ve got Varnish (cache server) running on the VPS which should mitigate “some” of it as far as images go. But that’s moreso to keep the reverse proxy on the VPS from having to request images all the way from my server box, thereby reducing latency some.

          • Burger@burggit.moeOPM
            4·
            1 year ago

            That being said, I’m glad the error page worked. It was @Disabled@burggit.moe 's idea. He coded up the html page (since I don’t know HTML at all) and I got it implemented on the VPS’s reverse proxy to intercept 500/502 errors and redirect to it.

  • Pink Bow@burggit.moe
    3·
    1 year ago

    Performing a search also brings a couple orange “couldnt_find_object” toasts. However, the search itself still seems to work fine, so this is extremely minor.

    • Burger@burggit.moeOPM
      4·
      1 year ago

      Good to know. Thank you for bringing this up. I went on another instance and tested this and it appears to happen there too. So it’s an upstream issue and not something that I introduced when we upgraded, which is a great relief.

  • RA2lover@burggit.moe
    2·
    1 year ago

    Checking mod-removed posts on the modlog returns a couldnt_find_post error instead of allowing them to be seen. Not sure if this is intentional but that was a tool whose accountability aspect i liked.

    • Disa@burggit.moeM
      4·
      1 year ago

      Checking on multiple accounts on this and other instances, the modlog loads for us, though we can only click through to the removed posts on an admin account. Is your issue specifically with trying to click through to see a removed post, or is it when trying to load the modlog at all?

      Here’s how the modlog currently looks when loading it on a test account (hidden under a spoiler for those who don’t want to see.)

      click to expand.

      Then when actually trying to click through to see a removed post I get the following error on the test account:

      This is the same across multiple instances, which are on the latest version of lemmy. Which tells us this might be an intentional change specifically to prevent regular users from seeing offending content. There doesn’t seem like there’s any easy way to remove this restriction on our end as it seems to just be part of the lemmy software.

      There does seem to be a new setting which is ticked automatically in the new update to hide mod names (probably to further reduce their accountability.) This, fortunately, is a setting, and we have unchecked it, so the names of the actual mods who did the actions should show up now.

      Hope this helps!~

      • RA2lover@burggit.moe
        6·
        1 year ago

        Doing a quick check on changes from 0.17.4 to 0.18, seems like the most probable culpirit are these lines from this commit.

        It doesn’t look like these changes were intentional either. Seems like the intent was on making deleted/removed posts not visible to non-mods/admins/creators on community post listings, rather than not visible at all.

        I’ve got zero experience with asynchronous rust (or rust, for that matter), but this doesn’t seem too hard to change (other than a potential distinction between removed and deleted posts). i’ll still need to figure out how to make sure the changes don’t break something else in the process, though.

    • Burger@burggit.moeOPM
      2·
      1 year ago

      Absolutely not. We don’t want to be opaque about anything when it comes to running this instance.

      It seems to be working for me both when logged in and logged out. Tried clearing your cache? The UI was updated since the recent update.

  • MomoNeedsCorrection@burggit.moe
    2·
    1 year ago

    I’m getting a problem where when I try to log in it says email verification is required, but I specifically didn’t connect an email to this. I went in and tried to attach a burner since I still have this login token up, but it says email isn’t supported on this instance. Help?

    Guess it fixed itself

      • Burger@burggit.moeOPM
        2·
        1 year ago

        Try now. I went into the DB and toggled your email as “verified” I’m somewhat concerned because I don’t see anything wrong with your account.

        • MomoNeedsCorrection@burggit.moe
          3·
          1 year ago

          Whatever happened, it ended up working fine. Thanks for actually being an admin that fixes problems instead of a reddit admin who problems what’s already good

  • porn@burggit.moe
    1·
    1 year ago

    Posting an extremely tall image (https://burggit.moe/post/84517) breaks webUI. the direct link to the image (https://burggit.moe/pictrs/image/186d3b6a-4b5d-4b97-85df-55f2f53f0700.jpeg) works, but webUI seemingly requests a webp conversion (https://burggit.moe/pictrs/image/186d3b6a-4b5d-4b97-85df-55f2f53f0700.jpeg?format=webp) which fails likely due to the dimensions.
    I assume this is probably a deeper lemmy issue, but posting here on the offchance therer is something like a setting for a webp conversion size limit you could increase.
    This is jpeg specific as far as I can tell