Looks like GitHub silently corrupted some index.

[pilif@mastodon.social]

@filippo 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]

@filippo
> just... not

Smells roboapprentice of the Sourcerer ;))

[unnick@booping.synth.download]

@filippo@abyssdomain.expert ive heard that commenting on a missing PR makes it appear like normal again

[tomsellers@infosec.exchange]

@filippo 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.

Incomplete pull request results in repositories

GitHub's Status Page - Incomplete pull request results in repositories.

(www.githubstatus.com)

[tmcfarlane@toot.community]

@filippo 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]

@filippo 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]

@filippo definitely saw PRs disappearing on my repos the other day. They did come back eventually.

[bmitch@fosstodon.org]

@filippo 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]

@filippo 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.

[kasperd@westergaard.social]

They also had an incident last week: https://www.githubstatus.com/incidents/zsg1lk7w13cf

[tomsellers@infosec.exchange]

@kasperd @filippo We subscribe to their Status alerts and it has been a very rough 10 days or so. We are also busy enough that we notice issues before GH posts about them or transient issues that never make it to the Status page.