Was hoping to see if anyone had encountered this issue, I’m running a single user instance for myself, and foolishly I forgot to set my lemmy docker images to not automatically update.

As of updating from 0.18.4 to 0.18.4-beta.8, Sync no longer works. I get a “failed to load” error

I certainly don’t mind waiting till the next stable release since this was my own fault, but wanted to see if anyone else was experiencing this

Update: It’s been fixed! Thanks so much ljdawson

    • Kizaing@lemmy.kizaing.caOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      I just tried, seems the migration only moves forward not backward :( I was able to revert it back to the beta.8 image without issue though.

      Looks like I might have to wait for a fix for now, but thanks!

      • redcalcium@lemmy.institute
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 year ago

        That’s a bummer. It seems while lemmy has the backward migration .sql files in their repo, the lemmy app itself only support forward migration and you’ll have to run the backward migration .sql files manually yourself in postgres.

  • andrew@lemmy.stuart.fun
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    What’s the version scheme here? You shouldn’t have a beta after a release is cut. I expected the next version to be 0.18.5-beta.1. Or an alpha at least.

    • Kizaing@lemmy.kizaing.caOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      I attempted to downgrade, it did not work haha. Seemed to have issues migrating the database backwards

  • EpicCreeper713@discuss.online
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Yeah my instance is using 0.18.4-beta.8 and Sync has stopped working for me too. I’m not the admin so I can’t really fix this

    • Kizaing@lemmy.kizaing.caOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Ah that’s too bad. I’m glad at least that it seems to be a reproducible issue. But hopefully it’s fixed soon, looks like we just have to wait it out

  • d3Xt3r@lemmy.nz
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    Someone here managed to get it working by clearing Sync’s cache, so maybe try that?