Discussions not displaying with filter is: open

[chrisgurney]

Discussion Type

Bug

Discussion Content

As of this morning (Oct 13), the discussions (600+) in my repo are not being displayed with filter is: open:
https://github.com/chrisgurney/obsidian-note-toolbar/discussions

They are still accessible if you remove the filter:
https://github.com/chrisgurney/obsidian-note-toolbar/discussions?discussions_q=

Per the problem posted here (7000 discussions just disappeared!) is the recommendation to open an issue and post the message per this comment? If so, where do I open the issue, if I don't have a paid account?

[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. ⭐

[Josverl]

Same issue on the MicroPython Discussion

[laymonage]

This has been going on for a while:

• https://github.com/orgs/community/discussions/202590
• https://github.com/orgs/community/discussions/202863
• https://github.com/orgs/community/discussions/154888#discussioncomment-17999649
• https://github.com/orgs/community/discussions/207901
• https://github.com/orgs/community/discussions/202863
• https://github.com/orgs/community/discussions/204806

Unfortunately, GitHub doesn't care.

[chrisgurney]

Based on the comments above I have closed and re-opened a number of discussions to get them to re-appear.

[Josverl]

I assume this is caused by effectively a DoS by AI,
But as a human I'd still like to be able to communicate with other humans without needing to reply to the 4.6K messages to revive them.

[chrisgurney]

Looks like it's possible to write a script to fetch a list of discussions, go through them one-by-one, and change their state to closed and back to open. I haven't tried it, but it's worth considering if GitHub itself isn't going to help resolve these indexing issues.

[Josverl]

Thanks - Whipped together a Q&D GH-CLI script to reactivate the recent active discussions.
I suggest to limit to a recent few months - as not to add too much load .
Also changes can also trigger webhooks or automation; they are not a side-effect-free “refresh.”

https://gist.github.com/Josverl/67bd65e9e7e76d06b82e8f4f9a62c11e

Limited testing - use with care.

[Josverl]

Running the script on our micropython/micropython Discussion for the 3 Months seems to have brought back many (not all) others as well.

OWNER=my-organization REPO=my-repository ./file-reactivate_disc.sh --period "3 months" --reactivate 

[insectengine]

Same on https://github.com/quarkusio/quarkus/discussions

[timothepoznanski]

Same issue here at Poznote repository -> https://github.com/timothepoznanski/poznote

A few hundred discussions in the repo but only a handful left in the search index, so the "Open" filter showed almost nothing while "All" still listed everything. 😖

Closing and reopening every discussion does bring them back, but I didn't want to do that because it can send two emails per discussion to everyone involved in it, the author, everyone who commented or replied, and everyone who subscribed. With hundreds of discussions that means a flood of emails for my users, all for a bug they have nothing to do with.

So I went with a gentler workaround. Adding a label to a discussion and removing it right away is enough to get it reindexed, and label changes don't send any email to anyone. The discussion shows up again under the Open filter within about 10 seconds, its state doesn't change and its "last updated" date doesn't move, so the sort order stays the same.

I ran it on 268 discussions and it took about 15 minutes. All of them are back in the index, with only one that needed a second pass.

I put the script I'm using in this gist https://gist.github.com/timothepoznanski/93d077683cfd0cd697d59b2adfd7fd3f

It needs Python 3 and the GitHub CLI (gh auth login) with write access to the repo. Set OWNER and NAME at the top, and change TEMP_LABELS if your repo doesn't have GitHub's default labels. It only touches the discussions missing from the search index, adds a label each one doesn't already have and removes it right away, retries when it hits rate limits, and checks at the end that every discussion has exactly the labels it had before.

Run it with --dry first to see what it would do, and run it a second time if a few are still missing.

This still doesn't fix the root cause, and discussions can drop out again if GitHub's index loses the repo once more...

[Josverl]

Nice, and quite subtle compared the my sledge approach⚒️

[BenkhiraAhmedBaderEddine1]

Hi,

This looks like a GitHub Discussions filtering bug rather than missing discussions, especially since the posts are still accessible when you remove the filter.

A similar issue has been reported in [GitHub Community Discussion #187194](https://github.com/orgs/community/discussions/187194), where open discussions were missing from the default Open filter but remained accessible when filters were cleared.

I'd recommend the following:

1. Check whether the affected discussions are still accessible through their direct links.
2. Try clearing all filters and refreshing the page.
3. If the issue persists, report it in [GitHub Community Discussions](https://github.com/orgs/community/discussions) and link the related reports so the GitHub team can investigate the filtering issue.

Since the discussions are still accessible, avoid deleting or recreating them. The problem may be with how GitHub indexes or filters discussions, rather than the discussions themselves.

Hope this helps!

[laymonage]

No it does not. AI slop.

[MaximilianSoerenPollak]

We had a similar problem and getting GitHub support to re-index the repo discussions fixed it.