this post was submitted on 28 Jun 2023
480 points (98.4% liked)

Lemmy.World Announcements

29079 readers
263 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news ๐Ÿ˜

Outages ๐Ÿ”ฅ

https://status.lemmy.world

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to info@lemmy.world e-mail.

Report contact

Donations ๐Ÿ’—

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Ko-Fi (Donate)

Bunq (Donate)

Open Collective backers and sponsors

Patreon

Join the team

founded 2 years ago
MODERATORS
ruud@lemmy.world
lwadmin@lemmy.world
lwCET@lemmy.world
jelloeater85@lemmy.world
Serinus@lemmy.world
lw_mod_notification@lemmy.world
MrKaplan@lemmy.world
480
[Update: Failed again] Update to 0.18.1-rc.1 tried and rolled back (lemmy.world)
submitted 1 year ago* (last edited 1 year ago) by ruud@lemmy.world to c/lemmyworld@lemmy.world
261 comments fedilink hide all child comments
 

We've upgraded lemmy.world to 0.18.1-rc.1 and rolled back that upgrade because of issues.

(If you had posted anything in those 10 minutes between upgrade and rollback, that post is gone. Sorry!)

The main issue we saw is that users can't login anymore. Existing sessions still worked, but new logins failed (from macos, ios and android. From linux and windows it worked)

Also new account creation didn't work.

I'll create an issue for the devs and retry once it's fixed.

Edit Contacted the devs, they tell me to try again with lemmy-ui at version 0.18.0. Will try again, brace for some downtime!

Edit 2 So we upgraded again, and it seemed to work nicely! But then it slowed down so much it was unuseable. There were many locks in the database. People reported many JSON errors. Sorry, we won't be on 0.18.1 any time soon I'm afraid..

you are viewing a single comment's thread
view the rest of the comments
[โ€“] FollyDolly@lemmy.world 1 points 1 year ago (2 children)

After the update I can no longer log in or interact with Jerboa. Hopefully y'all resolve this soon, as I am really digging Jerboa, but thanks for letting us know what's going on, and keeping up the good work.

[โ€“] jetsetdorito@lemmy.world 1 points 1 year ago

I've been using Jerboa since I joined a few weeks ago, I haven't been liking any of the other clients so far, but today I tried thunder and I'm enjoying it more than Jerboa

[โ€“] T156@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

There's a major breaking change in the 0.18 update (moving away from Websockets for posts and comments), that means that older Jerboa builds no longer work with instances on, or past, that version, and newer Jerboa builds won't work with servers older than 0.18.

[โ€“] Dran_Arcana@lemmy.world 2 points 1 year ago (2 children)

Version fracturing is probably going to be a fact of life on a decentralized platform like lemmy, a "good" app should probably handle cases for the latest few revisions instead of just the latest.

[โ€“] JonnyJ@lemmy.world 3 points 1 year ago

I'm sure it will eventually, but early stage tech needs some allowances while they handle growth and scale. Better to break stuff now than be hamstrung by tech debt years later

[โ€“] T156@lemmy.world 2 points 1 year ago (1 children)

It normally would, it's just that 0.18 is a breaking change, incorporating a major rewrite of how posts and comments work on Lemmy.

[โ€“] nerdyshades@lemmy.world 4 points 1 year ago (2 children)

I really like Semantic versioning. This would be from 0.17.X to 1.0.0 as it's a breaking change to the public API.

https://semver.org/

[โ€“] elxeno@lemm.ee 1 points 1 year ago

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

[โ€“] neblem@lemmy.world 1 points 1 year ago

Semver pre version 1 lets minor changes be breaking (points 4 & 5).