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

Android snapshot helper: a capture cancelled in its first milliseconds stalls the next capture

Aberta
  • Algo errado?
#4,030 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
72/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
android, typescript
Domínio
mobile, testing

Direção de pesquisa

Start with packages/platform-android/src/__tests__/snapshot-helper-session.test.ts and read the test named “cancels a stalled snapshot, retires its helper, and starts the next capture cleanly.” Trace how that test triggers cancellation and how the helper is retired or reused; the issue does not name the implementation file. Done means the test explicitly exercises cancellation at the risky early points and confirms the next capture starts within its normal budget.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

bug ready-for-agent

Found while working on #4021 (#4005). This happens on main's sources and was not introduced by that PR.

Symptom. In CI Coverage, packages/platform-android/src/__tests__/snapshot-helper-session.test.ts › "cancels a stalled snapshot, retires its helper, and starts the next capture cleanly" timed out at 5 s (run 40711232553).

Trigger. The test aborts the stalled capture with a fixed 10 ms timer. When the same flow is aborted 0–2 ms in instead, the next capture hangs for more than 3 s. This reproduces on main's sources and on #4021 alike. On a slow CI host the 10 ms abort lands early in the flow, which turns this into an intermittent timeout.

Possible product impact. If a real snapshot is cancelled right after it starts, the next capture on that device may stall instead of starting cleanly. That fits the "persistent session didn't answer" runs reported in #4005 and #3929.

Required behavior.

  • A capture cancelled at any point leaves the helper retired or reusable.
  • The next capture starts within its normal budget.
  • The test drives the abort at the risky points explicitly, rather than through a wall-clock timer.
Linguagem predominante
TypeScript
Estrelas
5.2k
Forks
359
Merge médio
12h 43min
PRs com merge (30d)
666

Preparar o ambiente

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 callstack/agent-device

Todas as issues de callstack/agent-device

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.