Release smoke run failed on every job for v0.1.1; three causes remain after #519
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
调研方向
Start with release-smoke.yml at lines 281 and 363, then compare its cosign-installer pin with release.yml. Read packaging/README.md and docs/install/container.md to check which release artifacts and image attestations are promised. The issue leaves decisions open about disabling deferred smoke jobs and producing an SBOM attestation; done means resolving those decisions and getting the 0.2.0 smoke run green.
由索引模型根据 Issue 内容生成。
描述
The smoke run after v0.1.1 (run 37169174068, Oct 4) failed in every job except tag parsing.
| Job | Failed at | Cause | Fixed by #519 |
|---|---|---|---|
pypi_smoke (darnit) |
Verify package is in the public set | Matrix said darnit, the package is darnit-core |
Yes |
pypi_smoke, other three |
Verify Sigstore attestation | Token uploads have no attestation | Yes |
container_smoke, both |
Set up job | Bad cosign-installer pin |
No |
binary_smoke, all three |
Set up job | Same bad pin | No |
homebrew_smoke, both |
Wait for darnit-tap PR to merge | No tap; waits 30 minutes, then fails | No |
plugin_structural_smoke |
Download plugin zip | The release produces no plugin zip | No |
What is left after #519
- Bad pin.
release-smoke.yml:281and:363pinsigstore/cosign-installer@0d05a4e36810cebf0e25e51fb1a4ee45ac1b75e2, which GitHub cannot resolve.release.ymlpins7e8b541eb2e61bf99390e1afd4be13a184e9ebc5for the same v3.10.1, and that one works. I will open a PR for this. - Homebrew, binary and plugin smoke jobs. They run on every stable release, but
release.ymldoes not produce those artifacts (packaging/README.mdmarks the channels as deferred). They will fail again on 0.2.0. Suggestion: switch them off until the channels exist. - Image SBOM attestation.
container_smokerunscosign verify-attestationon the image.release.ymlbuilds withsbom: falseand only runscosign sign. The step has never been reached because of point 1. I expect it to fail once the pin is fixed, but I have not confirmed that.docs/install/container.mdtells users every signed image has an SBOM attestation, so either the release creates one, or the smoke test and the docs stop mentioning it.
Points 2 and 3 need a decision. With them open, the smoke run for 0.2.0 will not be green even with #519 merged.
- 主要语言
- Python
- 星标
- 22
- 派生
- 27
- 平均合并
- 2 天 28 分钟
- 30 天内合并 PR
- 40
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
darnitdevorg/darnit 的其他 Issue
-
needs triage
难度 2/5 1-3 小时 新手友好度 78/100
darnitdevorg/darnit#589 ·
维护者通常 1 天内回复
-
needs triage
难度 2/5 1-3 小时 新手友好度 83/100
darnitdevorg/darnit#587 ·
维护者通常 1 天内回复
-
needs triage
难度 2/5 1-3 小时 新手友好度 65/100
darnitdevorg/darnit#585 ·
维护者通常 1 天内回复
-
quality
难度 2/5 1-3 小时 新手友好度 66/100
darnitdevorg/darnit#523 ·
维护者通常 1 天内回复
-
documentation good first issue
难度 2/5 1-3 小时 新手友好度 76/100
darnitdevorg/darnit#516 ·
维护者通常 1 天内回复
查看 darnitdevorg/darnit 的全部 Issue
相似的 Issue
-
area: agents area: docs good first issue
难度 2/5 1-3 小时 新手友好度 88/100
openapi/gknowledge#23 ·
-
get() for StrEnum可能已有人在做 @FeJo5952 今天认领。 未关闭good first issue
难度 2/5 1-3 小时 新手友好度 72/100
collective/icalendar#1921 · 1 条评论 ·
维护者通常 1 天内回复
-
Improvement Python Spans
难度 2/5 1-3 小时 新手友好度 68/100
getsentry/sentry-python#7994 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
alphagov/notifications-api#5004 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
equinor/radix-flux#3922 ·
维护者通常 1 天内回复