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

Releases do not check that each environment calls its own simulation service

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

Les mainteneurs répondent en général sous 3 jours

@anth-volk y travaille déjà.

Depuis le 21/10/2026.

  • #4003 par @anth-volk — ouverte

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
46/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
github-actions, python
Domaine
backend-api-design, ci-cd

Piste de recherche

Start by reading the staging and production model-version alignment jobs and the release workflow jobs that depend on them. Check how each job requests /health and reads response headers, then identify how the expected environment is represented in Cloud Run revision names. Done means each job fails for a missing or opposite-environment revision, and staging live simulation tests use the staging endpoint after the secret is updated.

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

Description

What

The Public API's staging environment calls the production Simulation Entrypoint. Its staging environment secret SIMULATION_ENTRYPOINT_URL resolves to https://simulation.api.policyengine.org, the same URL as production. As a result, the release workflow's live simulation tests against the staging candidate send their economy, budget-window and job requests to production simulation infrastructure, and staging simulation infrastructure receives none of them.

Nothing in the release workflow notices this. The staging and production model-version alignment jobs only ask the configured URL which bundle it supports; they never check which environment's service answers.

Wanted result

  • Each release checks that it calls its own environment's Simulation Entrypoint. The staging and production model-version alignment jobs read the x-policyengine-simulation-revision header from the selected URL's /health response, and fail if the Cloud Run revision belongs to the other environment's service, or if no revision is named.
  • Because every staging and production deploy job needs these alignment jobs, a release whose environments are crossed stops before it deploys.
  • Once the staging secret points at the staging Simulation Entrypoint, the staging live simulation tests run against staging simulation infrastructure and the staging Modal environment.

Order

The staging secret must first be changed to the staging Simulation Entrypoint's stable URL (after confirming that URL's /health names a policyengine-simulation-entry-staging-… revision). If the check merges before that change, every release fails at its staging alignment job.

Langage dominant
Python
Étoiles
18
Forks
33
Merge moyen
2 j 15 h
PR mergées (30 j)
35

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-api

Toutes les issues de PolicyEngine/policyengine-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.