microsoft / microsoft/vscode-pull-request-github

Connect timeouts and rate limit issues

Ouverte
#8,621 3 commentaires 1 réaction 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

info-needed
Langage dominant
TypeScript
Étoiles
2.6k
Forks
796
Merge moyen
1 j 4 h
PR mergées (30 j)
46

Description

  • Extension version: Any
  • VSCode Version: 1.112.0
  • OS: macOS 15.7.3
  • Repository Clone Configuration (single repository/fork of an upstream repository):
  • GitHub Product (GitHub.com/GitHub Enterprise version x.x.x): Github.com

When running the extension I frequently find it freezing or unresponsive when starting up. When checking the output logs of the extension I can see it's running either in connect timeouts or getting rate limited by Github. This seems like there's too much concurrent calls being made by the extension.

2026-03-30 09:25:15.269 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.270 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.270 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.271 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.271 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.271 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.272 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.272 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.273 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.276 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.277 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.277 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:26:30.164 [error] [GitHubRepository+0] Error querying GraphQL API (PullRequest): Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443. 
2026-03-30 09:26:30.165 [error] [GitHubRepository+0] Error querying GraphQL API (PullRequest): Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443. 
2026-03-30 09:26:30.165 [error] [GitHubRepository+0] Unable to fetch PR: Error: Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443
2026-03-30 09:26:30.165 [error] [GitHubRepository+0] Unable to fetch PR: Error: Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443
2026-03-30 09:26:30.165 [error] [GitHubRepository+0] Error querying GraphQL API (PullRequest): Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443. 
2026-03-30 09:26:30.165 [error] [GitHubRepository+0] Error querying GraphQL API (PullRequest): Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443. 
2026-03-30 09:26:30.166 [error] [GitHubRepository+0] Unable to fetch PR: Error: Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443
2026-03-30 09:26:30.166 [error] [GitHubRepository+0] Unable to fetch PR: Error: Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443
2026-03-30 09:26:30.166 [error] [GitHubRepository+0] Error querying GraphQL API (PullRequest): Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443. 
2026-03-30 09:26:30.166 [error] [GitHubRepository+0] Error querying GraphQL API (PullRequest): Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443. 

It's really frustrating to me. On the one hand the extension is really useful when it works properly, code navigation when reviewing from within your IDE is sublime. But the number of times the extension freezes or stops working after a new release makes it impossible to work with for me.

Steps to Reproduce:

  1. Open VSCode
  2. Try to load the extension

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Commencez au démarrage de l’extension et suivez les requêtes PullRequest de l’API GraphQL GitHubRepository décrites dans les logs. Reproduisez le gel avec les étapes VS Code indiquées tout en observant les appels concurrents, les erreurs de limitation de débit et les délais d’expiration de connexion. Le travail est terminé lorsque le démarrage ne surcharge plus GitHub et ne laisse plus l’extension sans réponse dans ce scénario.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
github, graphql, typescript, vscode
Domaine
api, devtools, networking
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
Calme
Clarté
À clarifier
Accessibilité débutants
38/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.