vscode-pull-request-github: Queries apart from "All Open" don't work, output is full of rate limit errors

  • Extension version: 0.76.1
  • VSCode Version: Version: 1.84.2 (Universal)
  • OS: macOs Sonoma 14.1 (23B74)
  • Repository Clone Configuration (single repository/fork of an upstream repository): fork of an upstream with multiple remotes
  • Github Product (Github.com/Github Enterprise version x.x.x): github.com

The viewlet currently lists the repo and its submodules, with some loaded PRs in the “All Open” section, not showing any pr’s content and the custom queries are not loading any PRs. The output shows a sea of rate-limiting errors

Steps to Reproduce:

The plugin didn’t ask for a login. just started loading the repo I’ve opened now (ceph) and all its submodules. I don’t know where it took the creds from, maybe from a token in my ~? The output below, and the graph QL rate limiting errors appeared within minutes after installing the plugin.

2023-11-21 13:09:40.359 [info] RateLimit> Extension rate limit remaining: 4, IssuesWithoutMilestone
2023-11-21 13:09:40.359 [info] RateLimit> Extension rate limit remaining: 3, IssuesWithoutMilestone
2023-11-21 13:09:40.359 [info] RateLimit> Extension rate limit remaining: 2, IssuesWithoutMilestone
2023-11-21 13:09:40.359 [info] RateLimit> Extension rate limit remaining: 1, IssuesWithoutMilestone
2023-11-21 13:09:40.359 [error] RateLimit> API call count has exceeded 140 concurrent calls.
2023-11-21 13:09:40.359 [error] RateLimit> API call count has exceeded 140 concurrent calls.
2023-11-21 13:09:40.359 [error] RateLimit> API call count has exceeded 140 concurrent calls.
2023-11-21 13:09:40.359 [error] RateLimit> API call count has exceeded 140 concurrent calls.
2023-11-21 13:09:40.361 [error] GitHubRepository> Unable to fetch issues: Error: Network error: Response not successful: Received status code 403
2023-11-21 13:09:40.361 [error] GitHubRepository> Unable to fetch issues: Error: Network error: Response not successful: Received status code 403
2023-11-21 13:09:40.361 [error] GitHubRepository> Unable to fetch issues: Error: Network error: Response not successful: Received status code 403
2023-11-21 13:09:40.361 [error] GitHubRepository> Unable to fetch issues: Error: Network error: Response not successful: Received status code 403
2023-11-21 13:09:40.361 [error] GitHubRepository> Unable to fetch issues: Error: Network error: Response not successful: Received status code 403
2023-11-21 13:09:40.362 [error] RateLimit> API call count has exceeded 140 concurrent calls.
2023-11-21 13:09:40.362 [error] RateLimit> API call count has exceeded 140 concurrent calls.
2023-11-21 13:09:40.362 [error] RateLimit> API call count has exceeded 140 concurrent calls.
2023-11-21 13:09:40.362 [error] RateLimit> API call count has exceeded 140 concurrent calls.
2023-11-21 13:09:40.362 [error] RateLimit> API call count has exceeded 140 concurrent calls.
2023-11-21 13:09:40.365 [error] GitHubRepository> Unable to fetch issues with query: Error: Network error: Response not successful: Received status code 403
2023-11-21 13:09:40.365 [error] GitHubRepository> Unable to fetch issues with query: Error: Network error: Response not successful: Received status code 403
2023-11-21 13:09:40.365 [error] GitHubRepository> Unable to fetch issues with query: Error: Network error: Response not successful: Received status code 403

tons of these now:

2023-11-21 13:19:10.729 [error] Error: GraphQL error: API rate limit exceeded for user ID <my user id>.
	at new e (/Users/leonidus/.vscode/extensions/github.vscode-pull-request-github-0.76.1/dist/extension.js:1837:140)
	...
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

About this issue

  • Original URL
  • State: closed
  • Created 7 months ago
  • Reactions: 1
  • Comments: 21 (10 by maintainers)

Commits related to this issue

Most upvoted comments

I’ve fixed a few submodules issues, but I’ve also found that in a multi-repo setup (includes submodules) that we’re refreshing the whole PRs tree way too often. Next fix will be to solve that.

It’s definitely the submodules then. The rate limit for “search”, which is the GitHub api we use for running those queries, is very low, but even if “search” had the standard rate limit I think you might still hit it. Thanks for all the info. Let me look into adding a way to ignore submodules and then I can work on better submodule support in general later.