Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#4,030 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
android, typescript
Área
mobile, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
TypeScript
Estrellas
5.2k
Forks
359
Merge medio
12 h 54 min
PR fusionados (30 d)
637

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de callstack/agent-device

Todos los issues de callstack/agent-device

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.