Keep staging candidate integration tests on the deployment runner
维护者通常 1 天内回复
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 52/100
调研方向
Start by reading the deployment workflow and its existing release tests; the issue does not name their file paths, so locate them in the repository. Trace how the tagged staging candidate is deployed, how the integration job gets its URL and staging database secret, and how downstream promotion is ordered. Add or update unit tests for the workflow ordering and dependencies; done means integration tests run in the deployment job while the listed release behavior is preserved.
由索引模型根据 Issue 内容生成。
描述
Deployment run https://github.com/PolicyEngine/policyengine-api/actions/runs/37626648234 failed twice because the tagged staging candidate scaled to zero while the integration job waited for a separate GitHub runner.
Cloud Run logs show that the first request then triggered a 205-253 second cold start, while the integration client stopped waiting after 90 seconds. The candidate eventually returned HTTP 200 in both attempts.
Acceptance criteria:
- Deploy the tagged staging candidate, wait for readiness, and run the deployed integration tests in the same GitHub job.
- Preserve the existing release tests, exact candidate URL, staging database secret, and downstream promotion ordering.
- Do not provision new infrastructure or change staging traffic.
- Cover the workflow ordering and dependencies with unit tests.
- 主要语言
- Python
- 星标
- 18
- 派生
- 33
- 平均合并
- 1 天 10 小时
- 30 天内合并 PR
- 20
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PolicyEngine/policyengine-api 的其他 Issue
-
Restore Scotland population live coverage with the fixed PolicyEngine bundle可能重新可做 关联的 PR 已关闭且未合并。 未关闭
难度 5/5 一周以上 新手友好度 25/100
PolicyEngine/policyengine-api#3876 ·
维护者通常 1 天内回复
-
State society-wide reports run on the sparse national dataset可能已有人在做 @anth-volk 于 6 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 35/100
PolicyEngine/policyengine-api#3864 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 38/100
PolicyEngine/policyengine-api#3823 ·
维护者通常 1 天内回复
-
API v2: report validations as an append-only, provenance-keyed resource on reports可能重新可做 @anth-volk 于 34 天前认领，目前没有进行中的 PR。 未关闭
PolicyEngine/policyengine-api#3818 · 已指派 1 人 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
PolicyEngine/policyengine-api#3816 ·
维护者通常 1 天内回复
查看 PolicyEngine/policyengine-api 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
spec-kitty/spec-kitty#6112 ·
维护者通常 1 天内回复
-
[Bug]: OpenRouter streaming chunks report the requested router name instead of the model OpenRouter served可能已有人在做 @Mrun25 今天认领。 未关闭bug llm translation
难度 2/5 1-3 小时 新手友好度 75/100
BerriAI/litellm#46095 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
uberdeveloper/fastbt#29 ·
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
andrew-blake/melcloudhome#368 ·
维护者通常 1 天内回复
-
lane:discover
难度 2/5 1-3 小时 新手友好度 72/100
SPARDiffData/differential-data-collection#33 ·
维护者通常 1 天内回复