Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Report job stages from the Stage 12 path

Aperta
  • Qualcosa non va?
#814 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
22/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend, testing-qa

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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).

Lingua principale
Python
Stelle
1
Fork
1
Merge medio
1g 8h
PR unite (30g)
52

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di PolicyEngine/policyengine-sim-api

Tutte le issue di PolicyEngine/policyengine-sim-api

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.