Post #1913846
2026-04-28 14:30 UTC
Replies (11)
-
@nim@mastodon.tetaneutral.net 2026-04-28 14:34
@filippo@abyssdomain.expert looks like https://www.githubstatus.com/incidents/zsg1lk7w13cf
-
@pilif@mastodon.social 2026-04-28 14:38
@filippo@abyssdomain.expert I got a notification about a comment on a commit being posted yesterday, but it still doesn't appear on the website GitHub is really struggling these days
-
@ohir@social.vivaldi.net 2026-04-28 14:40
@filippo@abyssdomain.expert > just... not Smells roboapprentice of the Sourcerer ;))
-
@unnick@booping.synth.download 2026-04-28 14:45
@filippo@abyssdomain.expert ive heard that commenting on a missing PR makes it appear like normal again
-
@TomSellers@infosec.exchange 2026-04-28 15:07
@filippo@abyssdomain.expert They've just posted a status update about this: After yesterday’s incident, we are investigating cases where /pulls and /repo/pulls pages are not showing all indexed pull requests. This is because our Elasticsearch cluster does not currently contain all indexed documents No pull request data has been lost. As pull requests are updated, they will be reindexed. We are also working on accelerating a full reindex so these pages return complete results again. https://www.githubstatus.com/incidents/x69zbgdyfzg0
-
@tmcfarlane@toot.community 2026-04-28 15:07
@filippo@abyssdomain.expert first time I clicked 237 didn't show in the closed list. I remove the closed filter, and check and saw it in the list, but then when I go back to the closed filter view it is now showing. We've been getting some random 502 on various GH hosted assets today, I wouldn't be surprised if there's some shit happening they haven't reported on yet.
-
@smira@fosstodon.org 2026-04-28 15:16
@filippo@abyssdomain.expert we had the same issue for our projects, it was literally showing no closed PRs. reaching out via support helped (GitHub had to manually rebuild the index for our repo).
-
@mellowfish@ruby.social 2026-04-28 16:51
@filippo@abyssdomain.expert definitely saw PRs disappearing on my repos the other day. They did come back eventually.
-
@bmitch@fosstodon.org 2026-04-28 17:43
@filippo@abyssdomain.expert I'm sure there's lots of flakiness happening at GitHub given all their news. But at least when I checked, the PR showed up in the list following your second link. Hopefully that means it's eventually consistent and now fixed, and not that there's a bad server you're hitting.
-
@edolnx@kind.social 2026-04-28 18:45
@filippo@abyssdomain.expert I am aware of several other folks experiencing the same problem over the last week. It's very unfortunate, but you are not alone in these issues.
-
@almad@fosstodon.org 2026-04-29 18:18
@filippo@abyssdomain.expert This is common for me, regularly also happens that authors do not see my CRs until they clear cache