Intermittent warnings during installation (Ubuntu)

未關閉
  • 哪裡不對？
#234 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
45/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
github-actions, typescript, ubuntu
領域
ci-cd, devops, operating-systems

研究方向

從 src/utils/setup/setupAptPack.ts 中大約第 190 行和第 199 行附近開始，這裡會準備 apt 金鑰並將產生的檔案傳遞給 chmod。檢查記錄的順序，並決定如何在 chmod 執行前驗證 keyring 檔案是否可用。在 Ubuntu 安裝期間不再出現間歇性的 chmod 失敗及由此產生的 GitHub Actions 警告，即表示完成。

由索引模型根據 Issue 內容生成。

描述

bug

When setup-cpp prepares the apt-keys using gpg..
https://github.com/aminya/setup-cpp/blob/290824452986e378826155f3379d31bce8753d76/src/utils/setup/setupAptPack.ts#L190

the created files are not always available on disk when chmod is run
https://github.com/aminya/setup-cpp/blob/290824452986e378826155f3379d31bce8753d76/src/utils/setup/setupAptPack.ts#L199

which produces annotations warnings in the run like:

Failed to add apt key via server keyserver.ubuntu.com: Error: Command failed with exit code 1: sudo 'chmod' '644' '/etc/apt/trusted.gpg.d/setup-cpp-ubuntu-archive.gpg'

This behavior is intermittent and probably dependent on how loaded the Github runner/machine is.
Is this a know issue or would it be feasible to have a check that the file exists before performing the chmod?

Example logs:

2024-03-13T16:32:43.5134503Z gpg: keybox '/root/.gnupg/pubring.kbx' created
2024-03-13T16:32:43.5574851Z gpg: keyring '/etc/apt/trusted.gpg.d/setup-cpp-ubuntu-archive.gpg' created
2024-03-13T16:32:43.5769405Z gpg: keyring '/etc/apt/trusted.gpg.d/launchpad-toolchain.gpg' created
2024-03-13T16:32:44.5382292Z gpg: key 1E9377A2BA9EF27F: public key "Launchpad Toolchain builds" imported
2024-03-13T16:32:44.5466832Z gpg: key 1E9377A2BA9EF27F: "Launchpad Toolchain builds" not changed
2024-03-13T16:32:44.5467907Z gpg: Total number processed: 1
2024-03-13T16:32:44.5468560Z gpg:              unchanged: 1
2024-03-13T16:32:44.6642692Z gpg: Total number processed: 1
2024-03-13T16:32:44.6643420Z gpg:               imported: 1
2024-03-13T16:32:44.7015884Z gpg: key 3B4FE6ACC0B21F32: public key "Ubuntu Archive Automatic Signing Key (2012) <[email protected]>" imported
2024-03-13T16:32:44.7017891Z gpg: Total number processed: 1
2024-03-13T16:32:44.7018903Z gpg:               imported: 1
2024-03-13T16:32:44.7027072Z gpg: key 3B4FE6ACC0B21F32: "Ubuntu Archive Automatic Signing Key (2012) <[email protected]>" not changed
2024-03-13T16:32:44.7028461Z gpg: Total number processed: 1
2024-03-13T16:32:44.7029174Z gpg:              unchanged: 1
2024-03-13T16:32:44.7096843Z chmod: cannot access '/etc/apt/trusted.gpg.d/setup-cpp-ubuntu-archive.gpg': No such file or directory
2024-03-13T16:32:44.7098787Z gpg: key 40976EAF437D05B5: public key "Ubuntu Archive Automatic Signing Key <[email protected]>" imported
2024-03-13T16:32:44.7108203Z gpg: Total number processed: 1
2024-03-13T16:32:44.7137810Z ##[warning]Failed to add apt key via server keyserver.ubuntu.com: Error: Command failed with exit code 1: sudo 'chmod' '644' '/etc/apt/trusted.gpg.d/setup-cpp-ubuntu-archive.gpg'
2024-03-13T16:32:44.7146153Z gpg:               imported: 1
2024-03-13T16:32:44.7156879Z gpg: key 40976EAF437D05B5: "Ubuntu Archive Automatic Signing Key <[email protected]>" not changed
2024-03-13T16:32:44.7158035Z gpg: Total number processed: 1
2024-03-13T16:32:44.7158753Z gpg:              unchanged: 1
主要語言
TypeScript
星號
277
分支
37
30 天內沒有已合併 PR

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

aminya/setup-cpp 的其他 Issue

查看 aminya/setup-cpp 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。