It seems api_tests is unstable, failing around half the time.... been that way for days it seems.
data loss... this has been going on for more weeks than I can count, and the developers with over 4 years experience are not the ones fixing such data-damage/data-loss bugs... just has been the pattern since Issue 2910 was ignored for months.
This gem of a quote: "That index is great, I didn't see that because on my database I guess the person table is too small for it to matter." https://github.com/LemmyNet/lemmy/pull/3960
That's exactly the problem with the whole project, no data, not concerned about data, ignoring all the problems on lemmy.ml since April despite 4 years of experience... data is not the focus of the project developers. lemmy.ml ran for 4 years on public Internet with nearly zero data. Not even a couple hundred megabytes of data.... and no testing and observation of problems with scaling and more data. It seems like they have 4 years of experience that isn't experience... just like Beehaw has shown with moderation experience and tools.
They ignored Issue 2910 for months during the critical Reddit API issue period, it worked fine with no data in the system, but was surely crashing lemmy.ml lemmy.world beehaw and all my test systems once even a modest amount of data is populated (it really does not take much)!
The logging that comes out of the Rust code on errors really says it all. Over 4.5 years of coding on the same project and running it on the live public Internet at lemmy.ml - and there is no way for a site operator/admin to view the Rust code failure logs without having to do all that independently (and no recommendations on the importance of viewing logs). And when GitHub issues get posted with log problems, the developers with all the Rust code experience ignore them.