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

Report job stages from the Stage 12 path

Abierto
  • ¿Algo no está bien?
#814 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
22/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, testing-qa

Línea de trabajo

Start with the policyengine_simulation_contract.job_progress module (JobStage, JobExecution, progress floors, progress_max) and the stage reporting from #781 on the run_simulation path, then find the Stage 12 coordinator and its baseline and reform workers. The open question is whether the public stages need a Stage 12 shape or whether simulating plus per-role detail is enough; settle that with maintainers first. Done means Stage 12 reports move through stages without going backwards, and projects/policyengine-apis-integ/tests/simulation/test_calculate.py covers a Stage 12 report.

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

Descripción

enhancement

Context

#781 adds client-visible job stages (queued, loading_data, baseline, reform, simulating, outputs) and progress / progress_max to GET /jobs/{job_id} for the current run_simulation path. The Stage 12 path (coordinator plus separate baseline and reform workers) does not report them yet.

As discussed on #781, Stage 12 parts are expected to carry into Stage 14, and stage reporting should go into both paths. Porting it later is fine.

Scope

  • Report stages from the Stage 12 coordinator for a report: preparation (loading_data), the concurrent baseline and reform workers, and aggregation (outputs).
  • Baseline and reform run at the same time in Stage 12, so they fit simulating better than separate baseline and reform stages. Decide whether the public stages need a Stage 12 shape, or whether simulating plus per-role detail is enough.
  • Reuse the contract in policyengine_simulation_contract.job_progress (JobStage, JobExecution, progress floors, progress_max) rather than adding a second one. Stage 12 report and simulation rows may be a better store than the Modal Dict.
  • Keep the guarantees from #781: progress never moves backwards (including re-runs), unknown stages are accepted by clients, and failures in reporting never change a result.
  • Extend the beta verification in projects/policyengine-apis-integ/tests/simulation/test_calculate.py to Stage 12 reports.

Not in scope

Runtime statistics (phase 2 of #780).

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.