Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Report job stages from the Stage 12 path

Offen
  • Stimmt etwas nicht?
#814 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
22/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
python
Bereich
backend, testing-qa

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

Vorherrschende Sprache
Python
Sterne
1
Forks
1
Ø Merge
1 T. 10 Std.
Gemergte PRs (30 T.)
53

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus PolicyEngine/policyengine-sim-api

Alle Issues in PolicyEngine/policyengine-sim-api

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.