Programming.Dev is going to be going down starting at around 00:01 UTC Monday Dec 2 to attempt to fix the database corruption that happened relating to communities.
This has been affecting attempting to look at the pages for certain communities (it would end up loading forever instead of actually showing the posts for the community) and was affecting federation in some cases.
This is the second attempt to fix the issues with the first one needing to be rollbacked from due to the fix not working.
This fix could take several hours, so the outage window is going to be from 00:01 - 06:00 Dec 2.
The fixes are done for tonight, but are not 100% complete. I estimate that 99.4% of cases have been fixed though. You might see problems with individual posts, but every community should be fixed. I’ve seen at least 1 issue with the !science@lemmy.world community and I’ll be investigating that if it doesn’t self resolve (stuff could still be catching up).
IF YOU SEE ANY MORE ISSUES PLEASE REPORT THEM HERE.
Edit: Definitely not relevant, it was a problem with the link I clicked
original
Not sure if it’s related but I’ve noticed a couple of smaller communities from other instances which aren’t accessible from programming.dev any more, Imaginary Witches and Imaginary Fairies. They give the very helpful error “unknown”, this might be a fun one to try to track down. They’re accessible on the source sites (1, 2) and other communities from those instances seem to work.
You should use /c/ and not /post/:
Ah, you’re right. I think I see what happened there, I hit those links from a sidebar in a community with href="imaginarywitches@lemmy.dbzer0.com"
which breaks if you’re on a post page instead of the community page. Easily fixed though, I’ll ping the mods of that community.
Heyo, I assume this may also be related to the database issue, but I noticed today that posts I make to !linuxhardware@programming.dev from slrpnk.net aren’t federating, nor are posts made there with my p.d account federating out to slrpnk.net.
https://programming.dev/c/programmer_humor, https://programming.dev/c/teach_programming, and https://programming.dev/c/data_structures still seem to be completely broken. Might need to investigate what’s happening for those as well.
Wait !programmer_humor@programming.dev is broken for you? For me in Jeroba that’s one of the communities that’s been working just fine this whole time, unless the recent maintenance broke it the last post I have is from yesterday.
EDIT: Ok, so clicking your link, or even my link gives an error saying community can’t be found but I can still pull it up from my subscriptions, so it was either broken by this maintenance or something weird is going on
I’ve not logged in for a couple of weeks. Is old.
deprecated now? Or is the fact that it won’t load any comments part of the corruption issue?
Aww man I just joined here recently, hopefully it’ll be fixed soon or won’t end up effecting newer communities.
I’m glad to hear that, I was a bit worried since I just started a community here. Do we know how it happened so we can avoid it in the future, or was it just bad luck?
To me (on voyager and on programming.dev website), !programming_languages@programming.dev still seems down
I thinki founda small issue though I can’t be sure it’s related to the corrupted data and yesterdays maintenance. It looks like a few of my community subscriptions are a little broken? FYI I’m using voyager on IOS.
As the server catches up, more content from the last two months has been showing up in my home feed. Fantastic! I decided that I don’t want to subscribe to !dailygames@lemmy.zip anymore. So I looked at my subscriptions, selected dailygames, tapped the “3 dots” menu button, and tried to unsubscribe. However, I subscribed again rather unsubscribed. I then looked at my subscribers again and saw daily games listed twice. Then, I unsubscribed using the same method but this only removed one instance of my subscription to dailygames.
So the content showed up in my home feed. My subscription was seemingly working fine. But I couldn’t unsubscribe as the subscription was not recognized in some contexts. It really feels like some crossed data in the database. Thankfully, this is a very small issue.
I have at least one more subscription that’s showing the same problem.
Lastly, I did find a solution. Voyager’s list of community subscriptions allows you to swipe on a specific community to unsubscribe from it. That worked just fine!