Discussions search index repeatedly dropped for yihui/yihui.org

[yihui]

Discussion Type

Bug

Discussion Content

Summary

The GitHub Discussions search index for this repository keeps losing almost all of its entries. The discussions themselves are fine — they still exist, remain open, and are reachable by direct URL — but anything that relies on Discussions search breaks: the
Discussions list page shows almost nothing. This has happened more than once.

Impact

The Discussions tab (https://github.com/yihui/yihui.org/discussions) displays only a handful of discussions instead of all of them.
Individual discussions remain fully accessible by number/URL (e.g. yihui/yihui.org#2071), confirming the data is intact and only the search index is affected.

Evidence

At the time of the outage, the discussion listing and the search index disagreed sharply. The listing API returned the full set:

{ repository(owner:"yihui", name:"yihui.org") { discussions(first:1) { totalCount } } }
# => totalCount: 1397   (1392 open, 5 closed)

But the search index returned almost nothing:

{ search(type:DISCUSSION, query:"repo:yihui/yihui.org", first:5) { discussionCount } }
# => discussionCount: 1   (only a single discussion indexed)

So ~1396 open discussions existed but were missing from the search index. Fetching any of the "missing" discussions directly by number worked normally.

Additional observation

Editing a discussion (any content change) re-adds that single discussion to the search index — i.e. the index is rebuilt per-discussion on write, but the bulk index had been dropped. I'm currently working around the outage by scripting a no-op edit to every discussion to force each back into the index, which is why the live discountCount is recovering — please treat the 1 vs 1397 discrepancy above as the real symptom.

Request

This has recurred multiple times, and each time I have to rebuild the index myself by touching every discussion, which isn't sustainable. Please investigate why the search index for this repository keeps getting dropped and fix it at the source, so the index stays intact and I no longer have to rebuild it by hand.

Thanks.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐