Version 0.19.X Deployment
Hello world!
I’m sure many of you fine folks have been wondering why we have not upgraded to version 0.19.X yet.
The whole team here has been getting asked this question quite a bit, from both members of the community and other instance admins. We want everyone to know, YES, we will upgrade to version 0.19.
We do not have a hard date set for when we will be upgrading as of yet, as we have about 7 associated task items that go along with this upgrade for things we need to double-check and confirm there will be no breakage.
Another big reason why we have not upgraded is due to reports from other instance admins that the front-end GUI can have performance issues. While a large portion of folks access our site using apps on their phones, we would rather not degrade the user experience for the rest of everyone else.
Worst case in terms of UI slowness, we would ask everyone to use either Alexandrite () or Photon () to mitigate the potential performance issues.
One final point to mention to address the delay is that we usually wait 1-2 weeks after a new release before applying it to production. This was complicated by the fact that there were multiple releases right after each other, with each new release having issues we hoped would be patched in the NEXT version. A new version would come up, and we would have to evaluate the stability and performance of it, which would take about 2 weeks, and then ANOTHER version would come out, which we would need to test. This was further complicated by the fact this was during the holiday season.
| Version | Release Date |
|---|---|
| 0.19.0 | 2023-12-15 |
| 0.19.1 | 2023-12-20 |
| 0.19.2 | 2024-01-10 |
| 0.19.3 | 2024-01-24 |
For us, stability is paramount, as we care very much about keeping everyone happy here.
While we can appreciate the rapid release of patches on 0.19, I hope everyone can now understand the delay. If all goes well, we will set a release day in the next week or two, most likely on a Saturday around 1800 UTC.
-jelloeater85
I just love how professional the Lemmy instances have become. They went from having stability issues to being extremely stable. I love our Lemmy community.
Keep up the good work!
I just love how professional the Lemmy instances have become.
Too bad upstream Lemmy development didn’t adapt. The early 0.19 releases left several big instances hanging with severe bugs leaving them practically unusable.
In the developers defense, there are some bugs that don’t appear until a a certain workload threshold is crossed. It’s entirely possible for code to pass all tests and yet break when under heavy load in the real world (which can be difficult to simulate).
Yeah many bugs are difficult to catch, but the federation and timestamp issue, was something different and almost like a joke that got out of hand.
the federation and timestamp issue, was something different and almost like a joke that got out of hand.
YOLO-driven development
The testing in production development
Everyone has a test enviroment, some are lucky to have a separate production enviroment
The testing in production development
That’s what Mastodon developers seem to do but ahead of formally releasing new versions and on their own instance only:
Lemmy devs have pushed RCs to lemmy.ml in the past.
Thank you for all your hard work!
Thanks for all this info, I knew running the largest Lemmy instance would be challenging in term of version upgrade, and I’m happy you keep us posted on all your plans! Keep up the good work!
Yeah, I think the transparency and inclusivity of this instance serves as a model. I love knowing that places like this can exist.
Thank you!
You’re welcome, and thank you too! 😊
No, YOU are welcome here ;) You guys make this instance and the fediverse the best ;D
Literally what we as admins feel like.
“Now it’s gonna take longer because you asked”
Correct
🐹🏆
Speaking as someone who is on an instance (lemmy.today) that ran into a bunch of breakage from the 0.19.X releases, and which still isn’t fully resolved, and where the instance admin said that he wished that he could downgrade to 0.18.X but couldn’t due to schema changes, I strongly endorse a conservative approach. The releases have not really met the bar that one might want for stability.
That’s especially true for lemmy.world, since it hosts a large chunk of the Fediverse communities, and if it has serious problems, there are gonna be spillover effects even on users elsewhere. I’d wait until less-critical instances have been the guinea pig for a bit on releases.
Seriously. Less is more.
There’s no need to keep up with the meme of releasing updates as quickly as possible.
Well said. I will happily forgo some new features for a while if it means that the overall experience is more consistent.
I’ve talked a lot of shit about the whole fediverse before, but I appreciate your stance towards stability. It’s what users crave! Thank you!
Leave the Gatorade for the plants…
Thanks for the update. I am looking forward to instance blocking!
Just don’t be too excited since it only blocks communities on instances, not the users on it.
Excerpt from Join-Lemmy.org
Users can now block instances. Similar to community blocks, it means that any posts from communities which are hosted on that instance are hidden. However the block doesn’t affect users from the blocked instance, their posts and comments can still be seen normally in other communities.
It’s still definitely useful, but it’s not as great as it’s been hyped, and won’t solve the spam problems from specific instances.
I am more interested in cleaning up All than the user brigade at this point.
I turned off nsfw due to all the porn and yiff, and I really would like to filter out instances that are in a language I don’t speak.
Yeah I just want to make sure people know so they don’t get their hopes up and get disappointed or frustrated that it doesn’t act like personal defederation.
That is very likely what I’ll use it for as well, since I basically stopped browsing all due to the NSFW communities who’s posts would pop-up randomly in it, sometimes even unflaired 😬.
filter out instances that are in a language I don’t speak.
I’d avoid that as it’s a bit overkill and many of those instances may also have English-speaking communities. A better solution is to exclude the languages you don’t speak from your settings so the posts and comments won’t appear for you.
exclude the languages you don’t speak from your settings
Thanks for the tip. This option is not surfaced in voyager, so I had no idea of its existence.
There is a warning that deselecting “unspecified” will remove most posts, so it remains to be seen how much this will help.
Yeah it would be good if more communities and instances chose to enforce setting a language, they can do that by excluding unspecified from their community which will disallow people to make posts there that don’t have the language set. Obviously nothing can be really done for posts that don’t set the language, as well as for most apps which don’t set the language whatsoever, or have really weird ways of doing it.
Good luck with the update! One great thing about 0.19 is that it allows users to check federation status between instances, will be awesome to get that for lemmy.world as well.
And one thing bad is that logged in users are logged out and can’t log back in, getting errors when loggin in or worse, the site showing them a server error and they think the site is down! All fixed by clearing cookies. Or in apps, logging out then back in.
It looks like 0.19.3 may have a fix for this, which is great. IMO it’s good that the largest lemmy instance hasn’t updated to 0.19 yet, because a bunch of users may have disappeared thinking the site was dead. And you’d never know, because 0.19 counts active users in a different way.
Hopefully this is the one, though!
allows users to check federation status between instances
Wait … what’s this?! Never heard of this as a user feature? Any guidance?
thanks!
Just so you know, there are some major security issues on 0.18. That’s why programming.dev immediately updated. The later bugs on 0.19 we were easily able to work around, while the security issues are major and should be resolved as soon as you can, as it affects every user.
We already patched it. No worries, we got already a tip for weeks. Sad that it got through the tests of the lemmy devs. Such issues should never go live.
Manually patched by pulling the commit and building your own source?
No, we just block the affected api endpoint
What are those security issues?
Slow and steady wins the race
No need to rush it if the software is in heavy churn. Just pick a date when the dust settles.
Hey just FYI, I’ve been experiencing a postgres memory leak issue on my instance since the upgrade to 0.19.2. Theres a GitHub issue open about it (#4406), not sure if it’s something that will affect you but probably worth keeping in mind
Hi,
thanks for the tip, we will look into this issue and check if it affects anything on our scale.
Yeah no problem, checked the issue – looks like there’s some movement on it so we’ll see
We are investigating another possible bug, that sorta spams other instances full of requests ( we say 5k requests per 5 seconds ) kinda like a DOS attack. We only saw this phenomena on 0.19.3 instances, and they are hitting us currently hard with many requests. We will have to block them until it gets fixed on their side.
Hmmmm interesting, i hope im not on the ban list! I haven’t noticed any weird traffic like that
Nope you are not ;)
We noticed it that it happens on smaller instances, that probably doesnt have the perfect hardware to run the 0.19 version and crashes => retries federation and they probably dont have a backoff strategy.
Because we noticed the site the domain was leading too wasnt responsive half of the time we tried to look if we can contact the admin.
LETSGO
Yeah my instance is small but my uptime is pretty good (except this db issue tbh) so that might be why
Thank you for looking out for us mobile/desktop web browser peasants. ❤️
I for one am thankful for the admins’ continued dedication to platform stability.
no rush. most don’t notice minor changes. thanks
