[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, ...)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 55/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- git, nodejs, typescript
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- Engine chatter leaks into rejections.
rush-client build -t nosuchprojprintsrush-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 atProductionDaemonRequestResolver.ts:111, 162, 190). Include only warning and error severities. - 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. - A typo in a
RUSH_DAEMON_*variable disables the escape hatch.RUSH_DAEMON_FOO=1 rush-client build --no-daemonand... rush-client --helpboth exit 1 withUnknown daemon environment variable "RUSH_DAEMON_FOO"., becauseresolveDaemonConfigurationruns before routing (launchClient.ts:43-46).--no-daemon,--helpand never-daemonize commands should not require a valid daemon configuration. - Misleading numeric error.
RUSH_DAEMON_QUEUE_TIMEOUT_SECONDS=-1reportsmust be a decimal number., because the regex rejects the sign before the range check (DaemonConfiguration.ts:131-132). - rush.json
daemonblock errors have no location.{"enabled":"yes"}reportsdaemon.enabled must be a boolean.Native schema errors include the file path and JSON pointer. - 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). rush-client daemon --helpanddaemon logs --helpexit 1. Help should exit 0. There's also a punctuation glitch in the fallback message:...require --no-daemon.; using in-process Rush.- Non-Git workspaces hard-fail instead of falling back. In a workspace that is not a Git checkout (tarball,
git archiveexport, a Docker context without.git), withRUSH_BUILD_CACHE_ENABLED=0, nativerush buildsucceeds, butrush-client buildexits 1 withroutingFailed ... 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 anunsupportedrejection 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 |
- 主要语言
- TypeScript
- 星标
- 6.5k
- 派生
- 710
- 平均合并
- 1 天 15 小时
- 30 天内合并 PR
- 37
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoft/rushstack 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
[rush] Upgrade the pnpm-sync-lib dependency to 0.3.5.可能已有人在做 @martinnaj 于 19 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
microsoft/rushstack#5971 · 2 条评论 ·
维护者通常 1 天内回复
查看 microsoft/rushstack 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
Koenkk/zigbee-herdsman-converters#13540 ·
维护者通常 1 天内回复
-
check:passed streams:add
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
area/busola/ux
难度 2/5 1-3 小时 新手友好度 68/100
kyma-project/busola#5442 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
vercel-labs/wterm#246 ·
维护者通常 1 天内回复