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

[rush] rush-cli-client/rushd: daemon-path error UX gaps (leaked engine chatter, transport jargon, RUSH_DAEMON_* typo blocks --no-daemon, non-Git workspaces hard-fail instead of falling back, ...)

Abierto
  • ¿Algo no está bien?
#6,075 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
55/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
git, nodejs, typescript
Área
cli, developer-experience, tooling

Línea de trabajo

Start by reading the issue's detailed list of problems and the referenced files: libraries/rush-daemon/src/EngineTerminalProvider.ts, apps/rush-cli-client/src/launchClient.ts, and DaemonConfiguration.ts. Reproduce one error, like the leaked engine chatter, by running a command with a non-existent project. Look at how errors are formatted and where they are wrapped. 'Done' means each listed UX gap is fixed, and daemon errors match native Rush's clarity.

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

Descripción

Summary

A bundle of daemon-path error-UX problems. Each one is small, but together they make daemon errors noticeably worse than native errors for both humans and AI agents. The items below were reproduced with rush-client from main @ 60007c9a8c and RUSH_DAEMON=1, and items 1, 3, 4 and 7 were independently confirmed.

  1. Engine chatter leaks into rejections. rush-client build -t nosuchproj prints rush-client: Daemon rejected the request (invalidRequest): Incremental strategy: cache restoration\n\nThe project name "nosuchproj" passed to "--to" does not exist in rush.json.\n\nAn error occurred. Native Rush prints only the middle sentence. Cause: EngineTerminalProvider.describeError (libraries/rush-daemon/src/EngineTerminalProvider.ts:19-24) prepends every buffered info/verbose line (used at ProductionDaemonRequestResolver.ts:111, 162, 190). Include only warning and error severities.
  2. Transport jargon prefix. Every daemon-side configuration or validation error is wrapped as Daemon rejected the request (routingFailed|invalidRequest): ... (apps/rush-cli-client/src/launchClient.ts:215-216). For user errors, print the native text and keep the code for --verbose.
  3. A typo in a RUSH_DAEMON_* variable disables the escape hatch. RUSH_DAEMON_FOO=1 rush-client build --no-daemon and ... rush-client --help both exit 1 with Unknown daemon environment variable "RUSH_DAEMON_FOO"., because resolveDaemonConfiguration runs before routing (launchClient.ts:43-46). --no-daemon, --help and never-daemonize commands should not require a valid daemon configuration.
  4. Misleading numeric error. RUSH_DAEMON_QUEUE_TIMEOUT_SECONDS=-1 reports must be a decimal number., because the regex rejects the sign before the range check (DaemonConfiguration.ts:131-132).
  5. rush.json daemon block errors have no location. {"enabled":"yes"} reports daemon.enabled must be a boolean. Native schema errors include the file path and JSON pointer.
  6. Duplicated error on fallback. A command-line.json syntax error prints the full error in the fallback notice, and then native Rush prints the identical error again (launchClient.ts:217-218).
  7. rush-client daemon --help and daemon logs --help exit 1. Help should exit 0. There's also a punctuation glitch in the fallback message: ...require --no-daemon.; using in-process Rush.
  8. Non-Git workspaces hard-fail instead of falling back. In a workspace that is not a Git checkout (tarball, git archive export, a Docker context without .git), with RUSH_BUILD_CACHE_ENABLED=0, native rush build succeeds, but rush-client build exits 1 with routingFailed ... The daemon engine requires a Git-backed workspace inputs snapshot. (right after "Rush will proceed without incremental build support"). Throw a typed error from rush-lib (PhasedScriptAction.ts:820-823) and map it to an unsupported rejection so that the client falls back in-process. (Item 8 was reproduced by one analysis run, and a prototype of the fix worked.)

Repro steps

See each item's command above. All of them were run in a synthetic workspace.

Expected result: Errors on the daemon path match native Rush's clarity and exit codes.

Actual result: As listed.

Details

This was found during an automated performance/behavior analysis of rush-client/rushd on Linux.

Standard questions

Question Answer
@microsoft/rush globally installed version? built from main @ 60007c9a8c (5.179.0)
rushVersion from rush.json? 5.179.0
pnpmVersion, npmVersion, or yarnVersion from rush.json? [email protected]
(if pnpm) useWorkspaces from pnpm-config.json? true
Operating system? Linux (WSL2 Ubuntu 24.04)
Would you consider contributing a PR? Yes
Node.js version (node -v)? 22.23.2
Lenguaje dominante
TypeScript
Estrellas
6.5k
Forks
710
Merge medio
1 d 15 h
PR fusionados (30 d)
37

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

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 microsoft/rushstack

Todos los issues de microsoft/rushstack

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.