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

Readiness wait: nightly soak and keep-or-drop rule

Abierto
  • ¿Algo no está bien?
#3,077 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
ci-cd, mobile-dev, performance, testing

Línea de trabajo

Start with the dependency in #3072 and the replay lane configuration that controls --debug. Verify that successful waited interactions expose data.readiness with polls and waitedMs, then record seven nightly runs, engaged waits, and wall-time p50 against the previous week. Finish by documenting the keep-or-drop decision here and applying the specified outcome.

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

Descripción

needs-triage

Part of #3069.

Purpose

#3072 gives replayed press/click/longpress steps a 2-second wait for a target that is not on screen yet. 46 local A/B runs never engaged it: every poll resolved on the first capture. The flake it targets lives on CI runners whose captures take seconds. This issue collects the evidence that decides whether the wait stays.

Required behavior

  • A successful interaction that waited reports it: data.readiness with polls and waitedMs, present only when polls > 1. Today the evidence reaches the request log only under --debug.
  • The nightly replay lane runs with --debug for seven nights after the PR merges.
  • After each night, count interaction_target_readiness diagnostics with polls > 1. Each one is a step that would have failed before the wait.

Completion conditions

  • Seven nights recorded in this issue: runs, engaged waits, wall-time p50 against the previous week.
  • Decision written here and applied:
    • Keep, if at least one night shows an engaged wait and p50 moved by less than 3%.
    • Drop, if no wait engaged in seven nights: remove readinessTimeoutMs, the replay default, and the targetReadiness cell, and keep the engine only where post-gesture and scroll use it.

Dependencies

Blocked by: #3072.

Lenguaje dominante
TypeScript
Estrellas
4.8k
Forks
315
Merge medio
11 h 27 min
PR fusionados (30 d)
556

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.