this post was submitted on 01 Dec 2024
35 points (100.0% liked)

Programming.dev Meta

2503 readers
2 users here now

Welcome to the Programming.Dev meta community!

This is a community for discussing things about programming.dev itself. Things like announcements, site help posts, site questions, etc. are all welcome here.

Links

Credits

founded 2 years ago
MODERATORS
[email protected]
[email protected]
35
Database Corruption Maintenance (00:01 - 06:00 UTC Dec 2) (stacks.programming.dev)
submitted 2 months ago by [email protected] to c/[email protected]
20 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 7 points 2 months ago (9 children)

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 [email protected] 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.

[โ€“] [email protected] 2 points 4 weeks ago

I think [email protected] may still be having some issues? From programming.dev it seems to infinitely load, but when clicking a link to visit from another instance, or refreshing the page, it shows an error of, "couldnt_find_community".

load more comments (8 replies)