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

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

Ouverte
  • Quelque chose ne va pas ?
#805 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é
2/5
Temps estimé
1-3 heures
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
python
Domaine
backend

Piste de recherche

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.

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

Description

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

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

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.