Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Report job stages from the Stage 12 path

Ouverte
  • Quelque chose ne va pas ?
#814 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
22/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
python
Domaine
backend, testing-qa

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
Python
Étoiles
1
Forks
1
Merge moyen
1 j 10 h
PR mergées (30 j)
53

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de PolicyEngine/policyengine-sim-api

Toutes les issues de PolicyEngine/policyengine-sim-api

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.