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

Move the worker to the bundle with the 2022–2036 SPM forecast

Abierto
  • ¿Algo no está bien?
#805 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
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend

Línea de trabajo

The work is in projects/policyengine-simulation-executor/pyproject.toml (the policyengine[models] pin) and tests/test_spm_runtime_native.py, in test_worker_year_boundary_matches_real_provider. It cannot start until the certifying policyengine.py release (spm-calculator 1.1.0) exists, so first confirm that release is published. Then bump the pin and move the three unavailable-year cases from 2036 to 2037, and run that test file. Done means the test passes and 2037 still returns SPM_YEAR_UNAVAILABLE.

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

Descripción

Part of the US 2036 extension, tracked in PolicyEngine/policyengine-api#3926. The worker reads its SPM year boundary from the installed provider, so 2036 becomes available as soon as the worker runs a bundle that certifies spm-calculator 1.1.0 (PolicyEngine/policyengine.py#618). No runtime code changes.

@anth-volk, the steps, once that bundle is released:

  1. Bundle bump. Move policyengine[models] in projects/policyengine-simulation-executor/pyproject.toml (now ==6.3.4) to the certifying release. If the policyengine.py release dispatch doesn't cover this repo, a manual pin PR does it.
  2. Tests. projects/policyengine-simulation-executor/tests/test_spm_runtime_native.py uses 2036 as the unavailable year in test_worker_year_boundary_matches_real_provider. Those cases become available, so move them to 2037:
    • {"time_period": "2037"};
    • {"start_year": "2037", "window_size": 1};
    • {"start_year": "2036", "window_size": 2}.
  3. Deploy order. Deploy the worker before or together with policyengine-api's bundle bump and PolicyEngine/policyengine-api#3928. The API checks that the worker's /versions match.
  4. policyengine-api-v2, if it's still deployed anywhere: it has the same executor layout, so mirror the test change there.

Staging checks:

  • A national 2036 economy run completes, and its SPM receipt includes "2036".
  • budget_window:2027:10 completes all ten years.
  • 2037 still returns SPM_YEAR_UNAVAILABLE.

🤖 Generated with Claude Code

Lenguaje dominante
Python
Estrellas
1
Forks
1
Merge medio
1 d 11 h
PR fusionados (30 d)
50

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.