Lemmy.ca's Main Community

2809 readers

1 users here now

Welcome to lemmy.ca's c/main!

Since everyone on lemmy.ca gets subscribed here, this is the place to chat about the goings on at lemmy.ca, support-type items, suggestions, etc.

Announcements can be found at https://lemmy.ca/c/meta

For support related to this instance, use https://lemmy.ca/c/lemmy_ca_support

founded 3 years ago

MODERATORS

[email protected]

Lemmy.ca scheduled maintenance Saturday July 6th (lemmy.ca)

submitted 4 months ago* (last edited 4 months ago) by [email protected] to c/[email protected]

18 comments fedilink hide all child comments

Hi everyone,

We'll be undergoing maintenance on Saturday morning from about 11am - noon PST.

We've been having some stability issues over the past few days that I've tracked down to database performance, so I'll be doing some tuning and also applying all our needed system updates at the same time.

Cheers!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 0 points 4 months ago* (last edited 4 months ago) (1 children)

Howdy! I know y'all probably have a plan for Saturday, but was hoping you could peek at another possible issue.

While I believe this might be a client issue (Connect), some communities from other instances are not being listed properly. So, being logged into lemmy.ca and then trying to list /c/cat on lemmy.world shows a strange list of posts that resembles /c/all.

This is not a widespread spread issue and may not happen when logged into other instances. (196 is another with a similar issue here, which is annoying as I prefer to monitor that community from this instance.)

Unfortunately, the Connect dev has been missing for a bit and we cannot verify where the issue actually is. (It would suck to switch client apps .. )

Thanks in advance!

[–] [email protected] 0 points 4 months ago* (last edited 4 months ago) (1 children)

You'll have to wait for the connect dev for that unfortunately

[–] [email protected] 0 points 4 months ago

It was kind of a stretch for it being an instance issue anyway, but thanks for the response. (These issues started after the last instance update, which does point the finger at the client in many cases. Not all, but many.)

Unfortunately, my manipulation skills are top tier. Unless you happen to have the memory span of a carrot, this issue report is now planted in your head as something to associate with any possible future issues that you might encounter. (I know how engineers think, bud.)

Ok, maybe I just have a little too much time on my hands at the moment to type out extended comments. ;)