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

Release smoke run failed on every job for v0.1.1; three causes remain after #519

Abierto
  • ¿Algo no está bien?
#593 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, github-actions, python
Área
ci-cd, release

Línea de trabajo

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.

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

Descripción

needs triage

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

  1. Bad pin. release-smoke.yml:281 and :363 pin sigstore/cosign-installer@0d05a4e36810cebf0e25e51fb1a4ee45ac1b75e2, which GitHub cannot resolve. release.yml pins 7e8b541eb2e61bf99390e1afd4be13a184e9ebc5 for the same v3.10.1, and that one works. I will open a PR for this.
  2. Homebrew, binary and plugin smoke jobs. They run on every stable release, but release.yml does not produce those artifacts (packaging/README.md marks the channels as deferred). They will fail again on 0.2.0. Suggestion: switch them off until the channels exist.
  3. Image SBOM attestation. container_smoke runs cosign verify-attestation on the image. release.yml builds with sbom: false and only runs cosign 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.md tells 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.

Lenguaje dominante
Python
Estrellas
22
Forks
27
Merge medio
2 d 28 min
PR fusionados (30 d)
40

Preparar el entorno

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 darnitdevorg/darnit

Todos los issues de darnitdevorg/darnit

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.