CI: probe-gate Playwright system-dep install (kill unconditional apt-get update per job)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- github-actions, typescript
- Área
- ci-cd
Línea de trabajo
Read .github/workflows/ci.yml and packages/everything-dev/src/services/scaffold/ownership.ts to understand the landed workflow change and why the file is framework-owned. Check ADR 0032 for the intended process for tying the local edit to the framework ship. Done means the framework-owned change can flow to generated children via bos sync, with actionlint passing.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Context
The 2026-10-23 CI incidents (three runs killed at the job timeout stuck in "Install Playwright system deps"; see plan 056 Phase 5) were band-aided with bounded retries. Root cause left in place: playwright install-deps chromium runs apt-get update + install unconditionally — even when every package is already present — so every browser job (5 per run) exposes itself to the apt network surface.
Change (landed in this repo's ci.yml)
Both Playwright jobs (dev and start matrix) now:
- Browser install (cache miss) —
playwright install chromiumdownload-only;--with-depsdropped. - Probe (always) —
playwright install-deps chromium --dry-run→ localapt-get install -ssimulation (no update, no network, no root; verified in playwright-core 1.63nativeDeps/reportMissingDependenciesLinux). Exit 0 = all present. - Bounded real install (conditional) — the existing 240s x 3 retry loop now only runs when the probe reports a non-font missing package. Font packages are exempt: Playwright's launch-time validation (
ldd) never checks them and the suites assert DOM text, not rendered glyphs. A probe failure with no package list (e.g. stale apt lists) degrades to the real install — same coverage as before, strictly less apt exposure.
Browsers remain cached on playwright-<OS>-<hashFiles(pnpm-lock.yaml)>; the probe list always derives from the installed Playwright version, so it stays in lockstep with the cache key.
Verification
actionlint(v1.7.7, same as the workflow-lint job) passes on all workflows.- First CI runs after landing double as the empirical probe of what the ubuntu-24.04 runner image ships: expect "Install Playwright system deps" skipped on all 5 browser jobs; the "Check Playwright system deps" log shows what (if anything) the image is missing.
Why filed here
.github/workflows/ci.yml is in the framework-owned inventory (packages/everything-dev/src/services/scaffold/ownership.ts), so this change flows outward to generated children via bos sync. Filed per ADR 0032 to keep the local edit and the framework ship tied together.
- Lenguaje dominante
- TypeScript
- Estrellas
- 5
- Forks
- 3
- Merge medio
- 9 h 35 min
- PR fusionados (30 d)
- 151
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de NEARBuilders/everything-dev
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
NEARBuilders/everything-dev#628 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
NEARBuilders/everything-dev#400 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
NEARBuilders/everything-dev#632 ·
Los mantenedores suelen responder en 1 día
-
Pinnable dev host slot for child CI — versioned host bundle URLs or a first-class local-host runnerAbiertoenhancement ready-for-agent
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
NEARBuilders/everything-dev#613 ·
Los mantenedores suelen responder en 1 día
-
documentation ready-for-agent
Dificultad 3/5 1-2 días Aptitud para principiantes 66/100
NEARBuilders/everything-dev#608 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de NEARBuilders/everything-dev
Issues similares
-
e2e-failure ready-to-code
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
redhat-developer/rhdh-plugin-export-overlays#4580 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
devdotfast/whiteboard#1415 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area/sessions comp/desktop desktop/sessions P2 type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
NousResearch/hermes-agent#145383 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
-
enhancement p2 setup
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
vercel/eve#5419 · 1 comentario ·
Los mantenedores suelen responder en 1 día