I’ll be restarting AZ today for an update to lemmy 0.19.

Upgrade complete.

This is a major upgrade, so I expect there to be some issues. Strap in, enjoy the ride.

Expect:

  • further restarts
  • bugs
  • slowdowns
  • logouts
  • 2FA being disabled
  • possibly issues with images, upgrading pictrs to 0.4 at the same time
      • BakuEnglish
        3·
        11 months ago

        My TPA (Boost) seems to no longer be showing karma amounts on user profiles. The update has broken whatever method boost used to extract that number, I presume?

        • Lodion 🇦🇺OPMA
          2·
          11 months ago

          That would be my guess. There have been pretty major changes to the API as I understand it.

        • NathA
          1·
          11 months ago

          I think I’m ok with this. I liked the initial concept of karma not being tracked long-term.

          I won’t really mind if the apps bring this data back, but I won’t lose sleep if it’s gone.

          • BakuEnglish
            1·
            11 months ago

            I don’t know, I kind of like having imaginary internet points, but maybe having it as an off by default toggle might be a good middle ground

      • maniacalmanicmaniaEnglish
        2·
        11 months ago

        2-factor authentication is no longer enabled as it was before the upgrade. I’m not sure if the 2FA code option on the enabling modal is part of setting up new authentication or for using old auth code and I haven’t tested it.

        • Lodion 🇦🇺OPMA
          4·
          11 months ago

          This was deliberate on the part of the devs. Old 2FA enrollment was finicky and error prone, locking many users out. So they’ve disabled it for everyone, forcing re-enrollment to enable it.

          • maniacalmanicmaniaEnglish
            2·
            11 months ago

            I think you made a guide for enabling this properly but I cannot seem to find it. Would that guide be deprecated now?

            • Lodion 🇦🇺OPMA
              2·
              11 months ago

              You’ve got a good memory. Yes, the new process is slightly different so the old guide isn’t relevant. Also its not as important anyway, enrolling no longer enables 2FA before you have a device capable of generating TOTP codes.

              • maniacalmanicmaniaEnglish
                2·
                11 months ago

                I see. I didn’t really understand the complication last time but appreciated the guide. Re-enrolling was a cinch. I best do the bot account. Anything about bot accounts we should know about after this upgrade?

                • Lodion 🇦🇺OPMA
                  2·
                  11 months ago

                  I didn’t see anything bot related from my skim of the change notes… should be fine.

                  • maniacalmanicmaniaEnglish
                    2·
                    11 months ago

                    Done. I don’t know if this counts as an issue but on Chrome after setting up 2FA, logging out and logging in to test if the 2FA prompt came up there was briefly a little red error pop up on the bottom left of the browser that said ‘Error: mising_totp_token’. Seems like something that should only come up after submitting a blank value not when the 2FA popup first appears. Probably something for the lemmy devs but sharing with you in case it’s config or other. No other issues to report so far. Thanks again.

      • maniacalmanicmaniaEnglish
        1·
        11 months ago

        OK. I might make add each issue as a separate comment. Let me know if you prefer they are combined.

        1. I get this when I try to access my profile
        • Lodion 🇦🇺OPMA
          1·
          11 months ago

          Spotted this one myself, but its not isolated to a user’s own profile. Suspect its a back end lemmy issue… will investigate.

          • Lodion 🇦🇺OPMA
            1·
            11 months ago

            Edit, nope… postgres docker memory issue… seems to be fixed after adding “shm_size: ‘1gb’” to the docker postgres compose stanza.