Releases do not check that each environment calls its own simulation service
维护者通常 3 天内回复
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 46/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, python
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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-revisionheader from the selected URL's/healthresponse, 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
stagingsecret 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.
- 主要语言
- Python
- 星标
- 18
- 派生
- 33
- 平均合并
- 2 天 18 小时
- 30 天内合并 PR
- 36
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PolicyEngine/policyengine-api 的其他 Issue
-
难度 1/5 1-3 小时 新手友好度 88/100
PolicyEngine/policyengine-api#3911 ·
维护者通常 3 天内回复
-
难度 1/5 1 小时以内 新手友好度 82/100
PolicyEngine/policyengine-api#3910 ·
维护者通常 3 天内回复
-
Remove the v1 user routes and keep complete simulation and report results final可能已有人在做 @MaxGhenis 今天认领。 未关闭
难度 4/5 3-5 天 新手友好度 45/100
PolicyEngine/policyengine-api#4028 ·
维护者通常 3 天内回复
-
Store the metadata v3 reads in the v2 catalog, from PolicyEngine.py's public records可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 4/5 3-5 天 新手友好度 48/100
PolicyEngine/policyengine-api#4022 ·
维护者通常 3 天内回复
-
Publish v2 catalog regions from the Public API's own region reference files可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 5/5 一周以上 新手友好度 38/100
PolicyEngine/policyengine-api#4019 ·
维护者通常 3 天内回复
查看 PolicyEngine/policyengine-api 的全部 Issue
相似的 Issue
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
fossasia/visdom-dev#77 ·
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
aws-cloudformation/cfn-lint#4890 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
volcengine/OpenViking#6521 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
-
bug
难度 2/5 1-3 小时 新手友好度 77/100
AstrBotDevs/AstrBot#10720 ·
维护者通常 1 天内回复