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

Expose the certified dataset SHA-256 and gate production on the served identity

Abierto
  • ¿Algo no está bien?
#742 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@MaxGhenis ya está trabajando en esto.

Desde el 11/10/2026.

  • #743 de @MaxGhenis — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
api, backend, devops

Línea de trabajo

Start with gateway_models.py, the executor bundle and routing state to trace how the certified default dataset SHA-256 can reach PolicyEngineBundle. Then inspect /versions, cloud-run-simulation-entry-smoke.sh, and the policyengine-release updater. Done means deployed bundle identities are exposed and checked on candidate and promotion, and the updater verifies the dispatch identity against the installed wheel and records the digests in its PR.

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

Descripción

For the UK Autumn Budget (28 October 2026), every number the simulation API serves must be traceable to the exact certified policyengine.py bundle and dataset bytes. Production must also be confirmed to serve that bundle before it counts as ready. Today:

  • The public PolicyEngineBundle schema (gateway_models.py) carries model and data versions but no dataset SHA-256.
  • /versions returns route maps only, with no per-bundle identity.
  • The deploy smoke (cloud-run-simulation-entry-smoke.sh) checks only that /versions responds.
  • The policyengine-release updater reads only client_payload.version, so it cannot confirm that the wheel it installs carries the bundle the release certified.

This issue covers the identity half of production readiness:

  1. Carry the certified default dataset SHA-256 from the installed policyengine.py bundle through the executor bundle, the routing state and PolicyEngineBundle.dataset_sha256.
  2. Expose each deployed wrapper version's bundle identity on /versions (bundles).
  3. Have the deploy smoke assert the expected identity: latest routes to the deployed policyengine version, with its UK model and dataset SHA-256, on the candidate and after promotion.
  4. Have the updater verify the release dispatch's bundle identity against the installed wheel and record the digests in the PR.

A numerical release sentinel and a tested rollback follow in a separate PR.

Lenguaje dominante
Python
Estrellas
1
Forks
1
Merge medio
1 d 6 h
PR fusionados (30 d)
24

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 PolicyEngine/policyengine-sim-api

Todos los issues de PolicyEngine/policyengine-sim-api

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.