A posting on the Instance-specific issues/observations about the upgrade: https://lemmy.ml/post/1444409
KNOWN BUGS
- Searching site-wide for “0.18” generates an error. This was working fine in 0.17.4 before Lemmy.ml upgraded: https://lemmy.ml/search?q=0.18&type=All&listingType=All&page=1&sort=TopAll
I’m curious why especially lemmy.ml wouldn’t wait for full release - surely after 6 RCs the full release is imminent?
Or of course, they’re stress testing it. Makes sense enough.
Wonder if I can finally sub to lemmy.ml communities…
lemmy.ml is official developer instance, makes moste sense to test it out here after dev servers.
It’s probably a combination of testing at scale on a server they control and wanting to get these features out so they can be iterated before a bunch of new users show up.
From my remote instance, I’ve been subbing to lemmy.ml communuites about every 2 or 3 minutes, and it just now started to jam up. I’m speculating that the server restart fixed the problem for the first hour or so, but now it’s back. Open GitHub Issue: https://github.com/LemmyNet/lemmy/issues/3101
It’s just so odd that only lemmy.ml communities seem to cause this. Lemmy.world is around as big or bigger and no issue there.
I think lemmy.ml has more posts, comments, likes in the database due to historic reasons - and the backend is timing out, PostgreSQL not keeping up to application timeout. I have seen the problem on Beehaw, Lemmy.world when they are busy and throwing nginx 500 errors on their front page.
I’ve also been seeing issues with subbing to lemmy.world communities from lemmy.ml, so I am not sure if it’s limited to just lemmy.ml communities.
I can confirm that.
Not long after you upgraded, I upgraded, and was able to successfully subscribe to things here.
But… not now. /sadface.