Thank you for the transparancy!

Thanks for all your hard work @[email protected]. It's not easy!

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.

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:

is that users can’t login anymore

Ouch, that's bad :(

Thank you for your work, as always :)

Thanks for the hard work /u/ruud, we'll get there

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?

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 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.

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?

@[email protected] 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.

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.

Eveyrthing (UI) is extremely slow now. Not an improvement at all.

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.

Running one of the largest and most vibrant Lemmy instances certainly makes this deployment a great test case for the devs and the system overall. @[email protected] this community really appreciates you!

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! 👍

Oh. Good luck with the next try!

Linux/Firefox After upgrade many things didn't work, but they continued not to work after rollback.

Turns out I needed to clear the cache, then everything worked fine again.

Thanks for the info. You're doing a great job!

Bummer. Other instances apparently managed to upgrade, but none has the scale of lemmy.world, so that was bound to stretch things to their breaking point. Hopefully the devs are on top of whatever's causing it!

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.

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.