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

Let a verified runtime trace from an allowlisted monitor conclude PASS for RE-02.01

Abierto
#553 1 comentario 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
52/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python

Línea de trabajo

Start by reading the step-type registration and RE-02.01 definitions, then inspect the corpus cases for reproducibility checks; the issue gives no file paths, so locate these through #453 and #227. Done when a separate Witness verification step is wired ahead of repro_hermetic_build, passes or fails as specified for verified attestations, returns ERROR when verification fails, and has corpus coverage.

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

Descripción

module-reproducibility needs triage

Feature 044 (#453) registers every reproducibility step type that decides from text or file-presence signals as FAIL-only. A PASS from those signals is evidence only.

repro_hermetic_build also verifies Witness attestations. A verified attestation that records no network access during the build is a cryptographic observation, not a text signal. Because it sits inside the same step type, it can no longer conclude PASS for RE-02.01 either.

Proposal:

  • Split Witness verification into its own step type with a {pass, fail} ceiling. It passes on a verified attestation with no recorded network access, fails on a verified attestation that records network access, and is ERROR when the attestation can't be verified.
  • Add it as an RE-02.01 step ahead of repro_hermetic_build.
  • Back it with corpus cases.

The signal-based checks in repro_hermetic_build stay FAIL-only.

Related: #453, #227. Paths change if #532 (rename to darnit-amber) lands first.

(Drafted with Claude Code.)

Lenguaje dominante
Python
Estrellas
22
Forks
27
Merge medio
1 d 20 h
PR fusionados (30 d)
39

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.