vscode-pull-request-github: Rate limit error

Type: Bug

I work for an org with github integrated SSO. I have a VS code session locally that was logged in 5 weeks ago, but holidays happened and I didn’t touch my company repos during that time - though I did do personal coding.

For some reason today, trying to create my first PR to company repos since the holidays, githib PR showed me a ‘log into github’ form.

But down the bottom under accounts, it showed me logged into github with the correct username.

Clicking on the sign in button in the PR side window, nothing happened.

I then used the accounts button to sign out, after which the sign in button brought up my browser, which I then logged into just fine. The link and bounce back to vscode however errored: vscode got

[Info  - 12:18:25.102] Getting sessions for read:user,repo,user:email,workflow...
[Info  - 12:18:25.102] Got 0 sessions for read:user,repo,user:email,workflow...
[Info  - 12:18:25.147] Getting sessions for read:user,repo,user:email...
[Info  - 12:18:25.147] Got 0 sessions for read:user,repo,user:email...
[Info  - 12:18:25.173] Getting sessions for read:user,repo,user:email,workflow...
[Info  - 12:18:25.173] Got 0 sessions for read:user,repo,user:email,workflow...
[Info  - 12:18:26.952] Logging in for the following scopes: read:user repo user:email workflow
[Info  - 12:18:26.959] Trying without local server... (read:user repo user:email workflow)
[Trace  - 12:18:33.367] Handling Uri...
[Info  - 12:18:33.367] Exchanging code for token...
[Info  - 12:18:33.666] Token exchange success!
[Info  - 12:18:33.666] Getting user info...
[Error  - 12:18:33.874] Getting account info failed: API rate limit exceeded for user ID xxx.
[Error  - 12:18:33.874] Error: API rate limit exceeded for user ID xxx.

Extension version: 0.48.0 VS Code version: Code 1.70.1 (6d9b74a70ca9c7733b29f0456fd8195364076dda, 2022-08-10T06:08:33.642Z) OS version: Windows_NT x64 10.0.22000 Modes: Remote OS version: Linux x64 5.13.0-52-generic Remote OS version: Linux x64 5.13.0-52-generic Remote OS version: Linux x64 5.13.0-1031-azure

System Info
Item Value
CPUs AMD Ryzen Threadripper 2990WX 32-Core Processor (64 x 2994)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 127.87GB (64.17GB free)
Process Argv –crash-reporter-id d9f3c32e-60ca-4766-805a-fb437a111084
Screen Reader no
VM 0%
Item Value
Remote SSH: tr2vm
OS Linux x64 5.13.0-52-generic
CPUs AMD Ryzen Threadripper 2990WX 32-Core Processor (64 x 2994)
Memory (System) 8.00GB (2.34GB free)
VM 0%
Item Value
Remote SSH: tr2vm
OS Linux x64 5.13.0-52-generic
CPUs AMD Ryzen Threadripper 2990WX 32-Core Processor (64 x 2994)
Memory (System) 8.00GB (2.34GB free)
VM 0%
Item Value
Remote SSH: cognite-lifeless
OS Linux x64 5.13.0-1031-azure
CPUs AMD Ryzen Threadripper 2990WX 32-Core Processor (32 x 2994)
Memory (System) 17.22GB (3.76GB free)
VM 0%
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627cf:30244335
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
wslgetstarted:30449410
cppdebug:30492333
vscaat:30438848
pylanb8912cf:30529770
vsclangdc:30486549
c4g48928:30535728
d7fjc500:30543455
dsvsc012cf:30540253

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 7
  • Comments: 26 (11 by maintainers)

Commits related to this issue

Most upvoted comments

I’m still facing the rate limit error in v0.78.1

API rate limit exceeded for user ID xxxx.

Log

2023-12-19 13:41:07.286 [debug] CreatePullRequestViewProvider> Creating pull request with args {"title":"xxxx","body":"xxxx","owner":"xxxx","repo":"xxxx","base":"master","compareBranch":"xxxx","compareOwner":"xxxx","compareRepo":"xxxx","draft":false,"autoMerge":false,"labels":[],"assignees":[],"reviewers":[]}
2023-12-19 13:41:07.298 [debug] GitHubRepository> Create pull request - enter
2023-12-19 13:41:07.299 [debug] GitHubRepository> Fetch metadata - enter
2023-12-19 13:41:07.299 [debug] GitHubRepository> Fetch metadata xxxx/xxxxx - done
2023-12-19 13:41:07.300 [debug] RateLimit> Extension rate limit remaining: 140, undefined
2023-12-19 13:41:07.796 [error] GitHubRepository> Unable to create PR: Error: GraphQL error: API rate limit exceeded for user ID xxxx.
2023-12-19 13:41:07.798 [error] FolderRepositoryManager+13> Creating pull requests failed: Error: GraphQL error: API rate limit exceeded for user ID xxxx.
2023-12-19 13:43:09.219 [debug] RateLimit> Extension rate limit remaining: 140, /repos/{owner}/{repo}/compare/{base}...{head}
2023-12-19 13:43:09.221 [debug] RateLimit> Extension rate limit remaining: 139, /repos/{owner}/{repo}/compare/{base}...{head}
2023-12-19 13:43:09.893 [debug] RateLimit> REST Rate limit remaining: 2595, /repos/{owner}/{repo}/compare/{base}...{head}
2023-12-19 13:43:09.899 [debug] RateLimit> REST Rate limit remaining: 2594, /repos/{owner}/{repo}/compare/{base}...{head}

I think it would be good if we had some button to open the GitHub PR creating page in the browser instead of creating it in the vscode

Saw this happening 3 times for me this week, this is quite a blocker.

I started getting a lot of notifications for API rate limit exceeded for user ID 131#### (masked) this week. I would like to provide any logs if I can on this. Please let me know how/where to add them and I will.

hmm, ok. We fetch a lot of data from GitHub after reload, so I was thinking that could be part of the problem. I’ve started seeing the rate limit this week too though. I’ll add some new logging around the rate limit and we’ll see what we can learn.