Thank you for the transparancy!
Lemmy.World Announcements
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
- DM https://lemmy.world/u/lwreport
- Email report@lemmy.world (PGP Supported)
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
Join the team
I love post like this, another reason of why this instance is so good
Thanks for all your hard work @ruud@lemmy.world. It's not easy!
is that users canβt login anymore
Ouch, that's bad :(
Thank you for your work, as always :)
I mean thatβs a Tuesday on Reddit lmao.
As any engineer who does ops can tell you - you did the right thing - the solution is always to roll back, never force a roll forward, ever.
We should totally do pre and post update parties though. Even if the update fails we can have an excuse for drinks and a fun thread.
UI: 0.18.0 BE: 0.18.1-rc.1 π
seems to be working for me, I was already logged on
Just curious, why are we updating now instead of waiting for the proper 0.18.1 release?
Because of a few things, really anoying bugs and the Jerboa app not working properly with older versions
Reasons I can think of:
-
The official Android client for lemmy, Jerboa, only supports 0.18 and later, unless users download older version from github and sideload manually.
-
Sorting is broken pre 0.18, new posts keeps flowing in.
-
Performance improvement by removing web socket from lemmy. (which fixes 2, which is why 1. happens)
Federation is completely borked with .18 servers. Its very difficult for us to interact with https://lemmy.ca in any way: subscribing, upvoting, comments, posting... its all bugged.
Its maybe not that big a deal because Lemmy.world "has the most users", so in some regards its https://lemmy.ca's loss but... we need to restore reliable federation... especially before the July 1st rush IMO.
The .17 to .18 upgrade is basically a soft-defederation event, because of whatever this bug is between the two versions.
I suspect there will be a large influx of new users in two days, and that having Jerboa not working on .world might cause a few issues
For example the frontpage is no longer being constantly filled with random posts when you set the filter to "active" or "top day".
Both Dessalines and Nutomic have been working their butts off to get 0.18.x ready for the Reddit API changes. Huge hopes they can pull through!
Dessalines:
Nutomic:
Suddenly my Jerboa won't change from local and I can't change the sort. Not sure if this is related, but it was working fine yesterday after I updated the app. But no longer this morning.
Oh. Good luck with the next try!
Thanks for the transparency. Maybe itβs a good idea to have a test instance and some test cases/validation done there before updating the main instance. This is a regular process in any software/tech company/stack.
Testing should never be done directly on the prod instance.
@ruud@lemmy.world just wondering if you have considered setting up a second, beta, instance of lemmy.world open to the public?
With all the performance issues with 0.18.1, it's highlighted that there needs to be a way to stress test these updates before applying them to the main instance.
Yes, considering that. But we'll need people to use that when we will do testing...
I am glad I didn't write my last post during the upgrade process.
Maybe next time, give a warning, or maintenance notice.
Thanks for trying though.
appreciate the transparency. how are things looking in the back in lemmy.world (server wise)? will we get to a point where it wont require complete rollbacks on the state when a botched update gets rolled out?
Jerboa is almost unusable for me at the moment. A lot of crashes, pages not loading, messages not sending etc. But I know that's inevitable at times. Restarting my phone seemed to make it worse. But I know you guys are on it! π
Iβve found from hopping around some other instances that have upgraded to 0.18 that it is still pretty buggy. It does seem to be giving more information about the errors, instead of just failing like in 0.17, but spend any time browsing on those instances and youβre bound to be inundated with JSON and query errors. It also seems to get worse the longer you browse.
The UI changes are nice, and I do appreciate not having my feed auto-updating constantly, but I think youβd be making the right choice to hold off on upgrading until they can iron 0.18.1 out all the way. Iβm not super knowledgeable about TS and Rust, but as a user it seems that switching from WebSocket created/shined a light on Lemmyβs issues with caching in general.
Thanks for the info. You're doing a great job!
I'm so new, I'm a baby, I have no idea what I'm doing. I did just create my account, I tried using the app but it wouldn't let me. Saying server version too low. I'm sorry for my ignorance, but is this what that means? And this means we can't use the app yet right?
Also, thank you for all of this. I will be here for it all, I'm staying forever! I already love this so much more than anything else π₯°
Jerboa crashes constantly for me now, doesn't even let me view anything. JSYK!
Sucks that lemmy.world won't be working with Jerboa when the reddit apps quit working in a couple days.
I am glad y'all rolled back. I had just enabled 2FA and could not login to my account. Rolling back removed 2FA so I was able to log back in. Thanks.
Seems 0.18 is up... and...
OH NO ! The interface changed ! Bring it back ! Bring it back... /s
Just kidding... It's looking good, so it's time to explore a little and find all the new stuff.
Nice work @Rudd, thanks for all the hard work.
My current session works now with 0.18.0 + 0.18.1.rc1
PSA: If you've been using lemmy.world during the upgrades and rollbacks your browser might've cashed some stuff that quickly got out of date. If you have problems (especially JSON errors), try doing a hard refresh (usually Ctrl + F5) on the site. It might log you out.
Looks like we're still having issues, more's the pity.
Do we know what's causing the issue, or is it still a bit of a mystery for the time being?