Improved error message when a required os lib is missing
维护者通常 1 天内回复
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 55/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, node.js, typescript, ubuntu
调研方向
Start by tracing the Node installation and verification flow in the action; the issue does not name specific files or tests. Check how the action handles a failed Node executable and whether it can identify a missing system library such as libatomic1. Done means a failure caused by a missing library gives a clearer error than exit code 127, with relevant tests covering that message.
由索引模型根据 Issue 内容生成。
描述
Description:
When trying to upgrade our application from node 24 to 26 the setup node failed with the following error:
Run actions/setup-node@v7
Attempting to download 26.12.1...
Not found in manifest. Falling back to download directly from Node
Acquiring 26.12.1 - x64 from https://nodejs.org/dist/v26.12.1/node-v26.12.1-linux-x64.tar.gz
Extracting ...
/usr/bin/tar xz --strip 1 --warning=no-unknown-keyword --overwrite -C /home/runner/_work/_temp/80f11687-6f0f-4adc-850c-6c97cf44d2e0 -f /home/runner/_work/_temp/e4551be6-f2d4-4553-8e19-c7704a200d29
Adding to the cache ...
Done
Error: Node installation failed. Node may not be installed or not on PATH: The process '/home/runner/_work/_tool/node/26.12.1/x64/bin/node' failed with exit code 127
I figured out that our self hosted runners based on Ubuntu 24.04 did not have the required lib libatomic1 installed. After installing this it worked as expected. This was introduced as a requirement in node 25.
What would be great would be if the action could provide me with a better error message like. Node failed to install because of a missing system lib. Instead of exit code 127
Justification:
To make it easier to find out why the install failed.
Are you willing to submit a PR?
Yes
- 主要语言
- TypeScript
- 星标
- 5k
- 派生
- 1.7k
- 平均合并
- 2 天 4 小时
- 30 天内合并 PR
- 1
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
actions/setup-node 的其他 Issue
-
feature request
难度 2/5 1-3 小时 新手友好度 65/100
actions/setup-node#1531 · 1 条评论 · 4 个 reaction ·
维护者通常 1 天内回复
-
feature request
难度 3/5 1-2 天 新手友好度 62/100
actions/setup-node#1657 · 2 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
When will the default npm be npm@12 instead of npm@11?可能已有人在做 @v-priyagupta108 于 4 天前认领。 未关闭feature request
难度 5/5 一周以上 新手友好度 30/100
actions/setup-node#1634 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Volta extends resolution in getNodeVersionFromFile has no cycle detection, recursing until stack overflow可能已有人在做 @v-gowridurgad 于 52 天前认领。 未关闭bug
actions/setup-node#1628 · 3 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
`npm config get cache` fails with `EBADDEVENGINES` when requiring newer npm versions in `devEngines`未关闭feature request
难度 4/5 3-5 天 新手友好度 52/100
actions/setup-node#1553 · 15 条评论 · 2 个 reaction ·
维护者通常 1 天内回复
查看 actions/setup-node 的全部 Issue
相似的 Issue
-
needs-area
难度 2/5 1-3 小时 新手友好度 68/100
Azure/typespec-azure#5936 ·
维护者通常 1 天内回复
-
难度 2/5 半天 新手友好度 72/100
vercel-labs/scriptc#2910 ·
维护者通常 1 天内回复
-
automation missing-model model-sync provider:fireworks-ai
难度 2/5 1-3 小时 新手友好度 72/100
anomalyco/models.dev#12458 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复