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

Flaky server tests on CI: DiagnosticsService startup error, ShowUI isolation browser start

Abierto
  • ¿Algo no está bien?
#209 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
45/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
bun, typescript
Área
backend, testing

Línea de trabajo

Start with src/server/__tests__/diagnostics-service.test.ts and src/server/__tests__/show-ui-isolation.test.ts, then read startServer in src/server/index.ts and the browser startup hook. Reproduce both failures on Linux by running each test in a loop and trace the startup errors and Chrome stderr handling. Done when the cause of each intermittent failure is fixed and both tests pass at least 50 consecutive runs on Linux.

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

Descripción

Two server tests fail on CI from time to time and pass on a rerun. Each one blocks unrelated PRs until someone reruns the job.

1. DiagnosticsService fatal startup error on stderr

DiagnosticsService > keeps fatal startup errors visible on stderr while recording diagnostics (src/server/__tests__/diagnostics-service.test.ts). It appears in 6 of the 7 failed runs of the CI workflow before 2026-10-29 (e.g. 40896064562, 39715621460, 39713535549, 39713507980, 39381580281, 39144653837). It passed 3 out of 3 times locally on macOS.

The test starts a server on a free port, then starts a second one on the same port and expects it to exit with Failed to start server. Is port <port> in use? on stderr. In the failing run, stderr had:

[Server] Uncaught exception:
Error
    at startServer (src/server/index.ts:380:15)

startServer (src/server/index.ts) catches the error from Bun.serve and rethrows new Error(message, { cause }), where message is the original message or the fallback text. The printed error has an empty message, so either the stderr was cut off, or the error reached the handler some other way than expected. The cause is not established.

2. ShowUI page frame isolation: browser did not start

page frame isolation in a real browser (src/server/__tests__/show-ui-isolation.test.ts, added in #207) failed in run 40905539947 (PR #211, which only changes the version and the CHANGELOG). The test launches headless Chrome with --remote-debugging-port=0 and waits up to 20 s for DevTools listening on on stderr. Chrome printed nothing in that time, so the hook failed with browser did not start and no isolation check ran. It passed in both CI runs of #207. The cause is not established: a slow cold start, a startup prompt, or output going somewhere else are all possible.

What to do

  • Reproduce each on Linux (the CI runner), for example by running the test in a loop.
  • Find the cause and fix it in the server or the test, without retries or a longer timeout that only hides it.
  • Done when each test passes in a loop of at least 50 runs on Linux.
Lenguaje dominante
TypeScript
Estrellas
490
Forks
47
Merge medio
10 h 40 min
PR fusionados (30 d)
83

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 GoDiao/dreamcoder

Todos los issues de GoDiao/dreamcoder

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.