Version 0.19.X Deployment

Hello world!

I’m sure many of you fine folks have been wondering why we have not upgraded to version 0.19.X yet.

The whole team here has been getting asked this question quite a bit, from both members of the community and other instance admins. We want everyone to know, YES, we will upgrade to version 0.19.

We do not have a hard date set for when we will be upgrading as of yet, as we have about 7 associated task items that go along with this upgrade for things we need to double-check and confirm there will be no breakage.

Another big reason why we have not upgraded is due to reports from other instance admins that the front-end GUI can have performance issues. While a large portion of folks access our site using apps on their phones, we would rather not degrade the user experience for the rest of everyone else.

Worst case in terms of UI slowness, we would ask everyone to use either Alexandrite () or Photon () to mitigate the potential performance issues.

One final point to mention to address the delay is that we usually wait 1-2 weeks after a new release before applying it to production. This was complicated by the fact that there were multiple releases right after each other, with each new release having issues we hoped would be patched in the NEXT version. A new version would come up, and we would have to evaluate the stability and performance of it, which would take about 2 weeks, and then ANOTHER version would come out, which we would need to test. This was further complicated by the fact this was during the holiday season.

Version Release Date
0.19.0 2023-12-15
0.19.1 2023-12-20
0.19.2 2024-01-10
0.19.3 2024-01-24

For us, stability is paramount, as we care very much about keeping everyone happy here.

While we can appreciate the rapid release of patches on 0.19, I hope everyone can now understand the delay. If all goes well, we will set a release day in the next week or two, most likely on a Saturday around 1800 UTC.

-jelloeater85

  • Mereo@lemmy.ca
    link
    fedilink
    arrow-up
    196
    ·
    8 months ago

    I just love how professional the Lemmy instances have become. They went from having stability issues to being extremely stable. I love our Lemmy community.

    Keep up the good work!

    • woelkchen@lemmy.world
      link
      fedilink
      arrow-up
      43
      arrow-down
      2
      ·
      8 months ago

      I just love how professional the Lemmy instances have become.

      Too bad upstream Lemmy development didn’t adapt. The early 0.19 releases left several big instances hanging with severe bugs leaving them practically unusable.

      • jimbo@lemmy.world
        link
        fedilink
        arrow-up
        77
        arrow-down
        2
        ·
        edit-2
        8 months ago

        In the developers defense, there are some bugs that don’t appear until a a certain workload threshold is crossed. It’s entirely possible for code to pass all tests and yet break when under heavy load in the real world (which can be difficult to simulate).

        • Rooki@lemmy.world
          link
          fedilink
          arrow-up
          16
          arrow-down
          2
          ·
          8 months ago

          Yeah many bugs are difficult to catch, but the federation and timestamp issue, was something different and almost like a joke that got out of hand.

  • Krafting@lemmy.world
    link
    fedilink
    arrow-up
    87
    ·
    8 months ago

    Thanks for all this info, I knew running the largest Lemmy instance would be challenging in term of version upgrade, and I’m happy you keep us posted on all your plans! Keep up the good work!

  • tal@lemmy.today
    link
    fedilink
    arrow-up
    64
    ·
    edit-2
    8 months ago

    Speaking as someone who is on an instance (lemmy.today) that ran into a bunch of breakage from the 0.19.X releases, and which still isn’t fully resolved, and where the instance admin said that he wished that he could downgrade to 0.18.X but couldn’t due to schema changes, I strongly endorse a conservative approach. The releases have not really met the bar that one might want for stability.

    That’s especially true for lemmy.world, since it hosts a large chunk of the Fediverse communities, and if it has serious problems, there are gonna be spillover effects even on users elsewhere. I’d wait until less-critical instances have been the guinea pig for a bit on releases.

    • maness300@lemmy.world
      link
      fedilink
      arrow-up
      15
      arrow-down
      1
      ·
      8 months ago

      Seriously. Less is more.

      There’s no need to keep up with the meme of releasing updates as quickly as possible.

    • ItsMeSpez@lemmy.world
      link
      fedilink
      arrow-up
      8
      ·
      8 months ago

      Well said. I will happily forgo some new features for a while if it means that the overall experience is more consistent.

  • deafboy@lemmy.world
    link
    fedilink
    arrow-up
    49
    arrow-down
    1
    ·
    8 months ago

    I’ve talked a lot of shit about the whole fediverse before, but I appreciate your stance towards stability. It’s what users crave! Thank you!

    • Draconic NEO@lemmy.world
      link
      fedilink
      arrow-up
      7
      arrow-down
      1
      ·
      8 months ago

      Just don’t be too excited since it only blocks communities on instances, not the users on it.

      Excerpt from Join-Lemmy.org

      Users can now block instances. Similar to community blocks, it means that any posts from communities which are hosted on that instance are hidden. However the block doesn’t affect users from the blocked instance, their posts and comments can still be seen normally in other communities.

      It’s still definitely useful, but it’s not as great as it’s been hyped, and won’t solve the spam problems from specific instances.

      • Xabis@lemmy.world
        link
        fedilink
        arrow-up
        10
        ·
        8 months ago

        I am more interested in cleaning up All than the user brigade at this point.

        I turned off nsfw due to all the porn and yiff, and I really would like to filter out instances that are in a language I don’t speak.

        • Draconic NEO@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          8 months ago

          Yeah I just want to make sure people know so they don’t get their hopes up and get disappointed or frustrated that it doesn’t act like personal defederation.

          That is very likely what I’ll use it for as well, since I basically stopped browsing all due to the NSFW communities who’s posts would pop-up randomly in it, sometimes even unflaired 😬.

          filter out instances that are in a language I don’t speak.

          I’d avoid that as it’s a bit overkill and many of those instances may also have English-speaking communities. A better solution is to exclude the languages you don’t speak from your settings so the posts and comments won’t appear for you.

          • Xabis@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            8 months ago

            exclude the languages you don’t speak from your settings

            Thanks for the tip. This option is not surfaced in voyager, so I had no idea of its existence.

            There is a warning that deselecting “unspecified” will remove most posts, so it remains to be seen how much this will help.

            • Draconic NEO@lemmy.world
              link
              fedilink
              arrow-up
              2
              ·
              8 months ago

              Yeah it would be good if more communities and instances chose to enforce setting a language, they can do that by excluding unspecified from their community which will disallow people to make posts there that don’t have the language set. Obviously nothing can be really done for posts that don’t set the language, as well as for most apps which don’t set the language whatsoever, or have really weird ways of doing it.

  • sunaurus@lemm.ee
    link
    fedilink
    arrow-up
    39
    ·
    8 months ago

    Good luck with the update! One great thing about 0.19 is that it allows users to check federation status between instances, will be awesome to get that for lemmy.world as well.

    • Dave@lemmy.nz
      link
      fedilink
      arrow-up
      20
      arrow-down
      1
      ·
      8 months ago

      And one thing bad is that logged in users are logged out and can’t log back in, getting errors when loggin in or worse, the site showing them a server error and they think the site is down! All fixed by clearing cookies. Or in apps, logging out then back in.

      It looks like 0.19.3 may have a fix for this, which is great. IMO it’s good that the largest lemmy instance hasn’t updated to 0.19 yet, because a bunch of users may have disappeared thinking the site was dead. And you’d never know, because 0.19 counts active users in a different way.

      Hopefully this is the one, though!

    • maegul (he/they)@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      8 months ago

      allows users to check federation status between instances

      Wait … what’s this?! Never heard of this as a user feature? Any guidance?

  • Desistance@lemmy.world
    link
    fedilink
    English
    arrow-up
    30
    ·
    8 months ago

    No need to rush it if the software is in heavy churn. Just pick a date when the dust settles.

  • snowe@programming.dev
    link
    fedilink
    arrow-up
    33
    arrow-down
    3
    ·
    8 months ago

    Just so you know, there are some major security issues on 0.18. That’s why programming.dev immediately updated. The later bugs on 0.19 we were easily able to work around, while the security issues are major and should be resolved as soon as you can, as it affects every user.

  • jivandabeast@lemmy.browntown.dev
    link
    fedilink
    arrow-up
    23
    ·
    8 months ago

    Hey just FYI, I’ve been experiencing a postgres memory leak issue on my instance since the upgrade to 0.19.2. Theres a GitHub issue open about it (#4406), not sure if it’s something that will affect you but probably worth keeping in mind

    • Rooki@lemmy.world
      link
      fedilink
      arrow-up
      14
      arrow-down
      1
      ·
      8 months ago

      Hi,

      thanks for the tip, we will look into this issue and check if it affects anything on our scale.

    • Rooki@lemmy.world
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      edit-2
      8 months ago

      We are investigating another possible bug, that sorta spams other instances full of requests ( we say 5k requests per 5 seconds ) kinda like a DOS attack. We only saw this phenomena on 0.19.3 instances, and they are hitting us currently hard with many requests. We will have to block them until it gets fixed on their side.

        • Rooki@lemmy.world
          link
          fedilink
          arrow-up
          3
          arrow-down
          1
          ·
          8 months ago

          Nope you are not ;)

          We noticed it that it happens on smaller instances, that probably doesnt have the perfect hardware to run the 0.19 version and crashes => retries federation and they probably dont have a backoff strategy.

          Because we noticed the site the domain was leading too wasnt responsive half of the time we tried to look if we can contact the admin.

  • QaspR@lemmy.world
    link
    fedilink
    arrow-up
    19
    ·
    8 months ago

    I for one am thankful for the admins’ continued dedication to platform stability.