Fetching pull request with query failed: HttpError: API rate limit exceeded

[nporcu]

I tried the Copilot Coding Agent for the first time today. After the second code review on a PR created by the coding agent, I hit this limit while commenting the changes. What is the issue? The PR changed 17 files and contains 10 conversations with 1-2 comments.

• Extension version: 0.116.2
• VSCode Version: 1.103.2
• OS: Windows 10
• Repository Clone Configuration (single repository/fork of an upstream repository):
• GitHub Product (GitHub.com/GitHub Enterprise version x.x.x):

Steps to Reproduce:

1. Create an issue in github.com
2. Assign Copilot Coding Agent as assignee
3. Let it finish its work
4. Add review comments to the PR
5. Letz it finish its work
6. Add comments again

Expected result: User is able to continuous his code review via the vscode pull request extension

Determined result: Exceeded the API rate limit and can't proceed the code review because of that

Rate limit request form the github API: { "resources": { "code_search": { "limit": 60, "remaining": 55, "reset": 1756589766, "used": 5, "resource": "code_search" }, "core": { "limit": 60, "remaining": 55, "reset": 1756589766, "used": 5, "resource": "core" }, "graphql": { "limit": 0, "remaining": 0, "reset": 1756590300, "used": 0, "resource": "graphql" }, "integration_manifest": { "limit": 5000, "remaining": 5000, "reset": 1756590300, "used": 0, "resource": "integration_manifest" }, "search": { "limit": 10, "remaining": 10, "reset": 1756586760, "used": 0, "resource": "search" } }, "rate": { "limit": 60, "remaining": 55, "reset": 1756589766, "used": 5, "resource": "core" } }

[JoeyZio]

I've been encountering the same issue - it seems to be hitting the API rate limit extremely fast. I tried leaving just two comments today and then hit the limit.

[wyattberlinic]

Adding on that I'm having the same issue. I've run into this twice in the last month or so. Reviewing PR's for around half an hour and I hit the rate limit. This extension seems to be fetching way to much data or way to frequently and runs into these limits quickly.

[marty0678]

Yeah just ran into this too after working for about 30 minutes, and leaving about a dozen comments. Seems the extension is over fetching when it doesn't need to.

[alexr00]

Folks, could you set the default log level for GitHub Pull Requests to "debug" (command "Developer: Set Log Level" -> GitHub Pull Request -> Use the double check next to "Debug" to set the default)

Then, next time you see the issue, please share the output from "GitHub Pull Request".