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

`supabase status` spins at ~160% CPU forever when stdout and stderr share a pipe whose reader closes early

Abierto
  • ¿Algo no está bien?
#6,846 1 comentario 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@7ttp ya está trabajando en esto.

Desde el 27/9/2026.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
67/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
cli

Línea de trabajo

Start by reproducing npx supabase status 2>&1 | head -3 and compare it with the non-hanging commands listed in the issue. Trace the supabase status handling of stdout and stderr when the shared pipe closes early. Done means the CLI exits instead of spinning after an EPIPE, while normal output and draining consumers still complete.

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

Descripción

🐛 Bug supabase/cli

Environment

  • Supabase CLI 2.116.0 (npm supabase, @supabase/cli-darwin-arm64); also observed on 2.118.0
  • macOS 27.0 (26A428), Apple Silicon (arm64)
  • Local stack running (supabase start)

Steps to reproduce

  1. npx supabase status 2>&1 | head -3

Expected

head prints three lines and exits; the CLI receives EPIPE/SIGPIPE on its next write and exits.

Actual

head exits, but the CLI process never does. It stays at 157-161% CPU until killed. sample shows the main thread looping in kevent64. Because the shell waits on every member of a pipeline, the command never completes. One background invocation ran for 14 hours before it was noticed.

Measurements (each run killed by a watchdog after 15-25 s)

Command Result
npx supabase status 2>&1 | head -3 hangs, 159.8% CPU after 24 s
npx supabase status 2>&1 | grep -q Stopped hangs, 157.5% CPU
node_modules/@supabase/cli-darwin-arm64/bin/supabase status 2>&1 | head -1 hangs, 161.2% CPU
npx supabase status 2>/dev/null | head -3 exits 0
npx supabase status 2>&1 >/dev/null | head -1 exits 0
npx supabase status 2>&1 | cat >/dev/null exits 0
X=$(npx supabase status -o json 2>/dev/null) exits 0

The hang requires both stdout and stderr in the same pipe, with a reader that closes before the CLI has finished writing. Piping only one stream, or draining everything, exits normally. Setting SUPABASE_NO_UPDATE_NOTIFIER=1 does not change the result.

Suggested fix

Exit (or stop writing) when a write to stdout or stderr fails with EPIPE, rather than retrying in the event loop.

Workaround

Capture the whole output first (X=$(supabase status -o json 2>/dev/null)) or redirect to a file, then read that.

Lenguaje dominante
TypeScript
Estrellas
2.4k
Forks
526
Merge medio
1 d 2 h
PR fusionados (30 d)
307

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 supabase/cli

Todos los issues de supabase/cli

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.