this post was submitted on 05 Sep 2023
11 points (100.0% liked)

Sync for Lemmy

15348 readers
14 users here now

๐Ÿ‘€


Welcome to Sync for Lemmy!

Download Sync for Lemmy


Welcome to the official Sync for Lemmy community.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Community Rules


1- No advertising or spam.

All types of advertising and spam are restricted in this community.



Community Credits

Artwork and community banner by: @[email protected]


founded 2 years ago
MODERATORS
 

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

top 12 comments
sorted by: hot top controversial new old
[โ€“] [email protected] 4 points 2 years ago (1 children)

Lemmy seems to support backward database migration (at least judging from the database migration script here), so you might be able to revert to v0.18.4 (backup your database first if you haven't already).

[โ€“] [email protected] 2 points 2 years ago (1 children)

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!

[โ€“] [email protected] 4 points 2 years 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.

[โ€“] [email protected] 3 points 2 years ago (1 children)

How are you installing the docker image? You can downgrade to the stable version.

[โ€“] [email protected] 2 points 2 years ago

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

[โ€“] [email protected] 3 points 2 years ago (2 children)

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.

[โ€“] [email protected] 2 points 2 years ago
[โ€“] [email protected] 2 points 2 years ago

The latest tag is mapped to 0.18.4-beta.8, I had it set to latest and my watchtower upgraded it from 0.18.4, I find it weird too

[โ€“] [email protected] 2 points 2 years ago (1 children)

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

[โ€“] [email protected] 1 points 2 years 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

[โ€“] [email protected] 1 points 2 years ago* (last edited 2 years ago) (1 children)

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

[โ€“] [email protected] 1 points 2 years ago

Clearing the cache seemed to have no effect :(