Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Copilot PR-state polling throws RangeError: Invalid array length while accumulating paginated results

Aberta
  • Algo errado?
#9,023 0 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@alexr00 já está trabalhando nisso.

Desde 6/10/2026.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

  • Extension version: GitHub Pull Requests 0.166.1
  • VSCode Version: 1.141.0-insider; also observed after updating to d1f9096c3663d21e55cf448de012c620b960220a on 6 October 2026
  • OS: macOS 27.0.1, Apple Silicon
  • Repository Clone Configuration (single repository/fork of an upstream repository): Multiple repositories/worktrees and windows, including the Agents window
  • GitHub Product (GitHub.com/GitHub Enterprise version x.x.x): GitHub.com

Steps to Reproduce:

An exact minimal reproduction has not yet been isolated. This report comes from retained logs during normal multi-window/Agents-window use, not from a new controlled reproduction.

  1. Use the affected extension with PR/Copilot-state polling active across repositories/worktrees.
  2. Observe background polling failures in the extension-host log. A useful targeted reproduction is a query that has multiple pages, particularly after the Copilot state model has initialized.
Observed

Ten RangeError: Invalid array length exceptions were recorded during 4 October 2026 13:14 to 6 October 2026 13:14 CEST (UTC+02). Renderer copies of the same exceptions were not counted again. The failure persisted after the latest Insiders update, with examples at 6 October 12:49:17, 12:51:41, and 13:08:28 CEST.

2026-10-06 12:49:17.147 [error] RangeError: Invalid array length
    at Array.push (<anonymous>)
    at <extensions>/github.vscode-pull-request-github-0.166.1/dist/extension.js:4168:41690
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async O6._pollForChanges (<extensions>/github.vscode-pull-request-github-0.166.1/dist/extension.js:3794:58246)

Paths are redacted; the error, timestamps, and bundled source locations are preserved. The failure interrupts background Copilot/PR-state refresh and may involve a very large accumulated array; no heap measurement has been taken.

Likely cause to investigate

Inspection of the installed bundle maps the failing push to refreshCopilotStateChanges. It loops while hasMorePages and appends the result of getPullRequestsForQuery. The helper can return cached or cumulative results, while the argument used for fetchNextPage is derived from the model's initialization state rather than advancing explicitly with each loop iteration.

This suggests repeated accumulation of the same/cumulative page when hasMorePages stays true. This is a code-and-stack hypothesis, not yet a regression-tested diagnosis.

Expected / proposed direction

Polling should advance pagination, terminate, and accumulate each PR once without unbounded array growth. Please check cached versus incremental query-result semantics and add regression coverage for an initialized model with more than one page, including a non-advancing result.

Raw logs are not attached because they contain unrelated private workspace/session data.

Linguagem predominante
TypeScript
Estrelas
2.6k
Forks
800
Merge médio
20h 52min
PRs com merge (30d)
35

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de microsoft/vscode-pull-request-github

Todas as issues de microsoft/vscode-pull-request-github

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.