4
Another rollback?
(media.tenor.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Jun 2023
4 points (100.0% liked)
Lemmy.world Support
3191 readers
10 users here now
Lemmy.world Support
Welcome to the official Lemmy.world Support community! Post your issues or questions about Lemmy.world here.
This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.
This community is subject to the rules defined here for lemmy.world.
To open a support ticket
You can also DM https://lemmy.world/u/lwreport or email report@lemmy.world (PGP Supported) if you need to reach our directly to the admin team.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world
founded 1 year ago
MODERATORS
Everything was beautiful for a minute there.
I found the
UI 0.18.0 | BE 0.18.1-rc.1combination to be awfully slow and buggy.Why not just update both Backend (BE) and Frontend (UI) to
0.18.0and disable signups until0.18.1is released? I mean,lemmy.worldreally doesn't suffer from not having enough users, right?0.18.0 would have given us the same issues we experienced today. We tried everyhing on a test-instance before but once the live was upgraded it went from good to bad very fast. Json errors, 2FA issues and then the slowness.
When do you expect to turn into the next u/spez. Are we talking years or months or weeks?
Are you a fan of Elon Musk?
Are you American?
Which political party do you support?
Do you have lop-sided eyes and invisible eye brows?
What are you on about and what does that have to do with the rollback? :)
This is kinda odd since
lemm.mlis running0.18.0on both BE and UI for quite a while now. Also I got the foillowing error message quite frequently and the UI was unresponsive until I refreshed the browser window. But maybe this was whileUI 0.18.0was active withBE 0.17.4. Looks like now eveyrthing is back to0.17.4.Update: Looks like deleting all
lemmy.worldsite data in my browser (chrome) and logging in again solved this issue.