A section on my main page is showing "Could not fetch pull requests for this section. If this issue persists, try updating your filters.". It happens to various members of my team and happens to different sections. Standard stuff (clearing cache, restarting browser, rebooting) doesn't seem to work. Anybody else seen this? Any workarounds?

(If applicable) To help us repro, please send the following if you haven't already: - PR links, screenshots, and/or debug output if applicable - Repro steps - Does this happen consistently? Just to you or others on your team also? - Is this a regression? Is the problem new? - If you're having an issue with the CLI, please send us debug logs using

gt feedback --with-debug-context <any message>

Any update on this? It's still happening.

thanks for the bump here Adam, ive followed up with the team for an update.

hey Adam, I'm going to raise this with the team again this week. Apologies for the delays here

Two months, no progress? Should I just assume this will never get fixed?

Adam, could you try reducing the time window in your filters? This came up in another thread and adding a time window helped for the other reporter.

If I add "Latest activity less than: 1 week ago" to both existing filters, it correctly lists none. If I set it to "1 month ago", the error reappears. I don't have a huge number of PRs, so I doubt the problem is the sheer quantity. Note I never attempted to edit the filter until the error appeared, so I believe it's the default for "Waiting for reviewers". I tried creating a new section from a coworker who shared his filters, but the same error occurs. This seems to indicate it's a problem with one of my PRs, since it doesn't happen for him.

interesting. It does feel like there is a specific PR causing the issue though the error i see under the hood is

Query exceeded row limit threshold 5000

 why i suggested the date filter. Will bump the eng team on this again.

Hmm. I can do a filter with just the condition "Author is: janinreflex" and it works fine. According to github, there should be 304.

okay i think ive identified the issue here. Seems like for some reason PR

2831

has an abnormal amount of CI check runs in our DB for

headSha

=

6b91afb1de89eb48d51fa23669ec784168bef709

... over 5,000! Its unclear to me why, and surely we could handle htis better but i think you could either pusha new commit to this PR OR close it (seems kinda old) which should resolve this failing request.

I was unable to open the PR in Graphite. I closed it from github. Now, a different sections is failing to load. Maybe it'll take less than 8 months to fix it this time?

MY guess is this is the same issue based on the logs. Its that one PR just moved to a different inbox section. You can add "is not closed" to the section probably.