Give the Simulation Entrypoint its own simulation schema, migration chain and database connection
維護者通常 1 天內回覆
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 15/100
研究方向
Start by reading the Simulation Entrypoint deployment and readiness checks, the repository's migration ownership rules, and existing Alembic and PostgreSQL CI configuration. The issue names migrations/ as the chain location and SIMULATION_DATABASE_URL as the runtime setting; first confirm the staging and production roles, URLs, and grants have been created. Done means the entrypoint deploys with an empty simulation schema at its first revision, readiness reports that revision, the candidate check matches it to the image, and CI completes the upgrade, check, downgrade, and upgrade cycle.
由索引模型根據 Issue 內容生成。
描述
The Simulation Entrypoint will record simulations, reports, their runs and their results in its own Postgres schema, simulation, in the database that holds the Public API's v2 tables. Before any table can be added, the service needs the foundation:
- a persistence library for that schema, with its own Alembic migration chain;
- a migration job that applies the chain before each entrypoint deploy, using a separate migrator role;
- the runtime role's database URL (
SIMULATION_DATABASE_URL) mounted on the entrypoint as a pinned Secret Manager version; - the schema's applied revision reported by the readiness check, and required by the candidate check to match the image;
- ownership rules in place of the rule that forbade any migration chain in this repository: one chain at
migrations/, its version table in thesimulationschema, the Modal executor and gateway independent of the library, and no database URL in Modal except the Stage 12 comparison path's own; - a CI job that runs the chain's upgrade, check, downgrade and upgrade cycle on PostgreSQL.
Once deployed, the entrypoint has a database connection and an empty simulation schema at its first revision; nothing reads or writes it yet. The database roles, URLs and grants must be created by an operator in staging and production first.
- 主要語言
- Python
- 星號
- 1
- 分支
- 1
- 平均合併
- 1 天 17 小時
- 30 天內合併 PR
- 60
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
PolicyEngine/policyengine-sim-api 的其他 Issue
-
Update policyengine to 6.7.3可能重新可做 關聯的 PR 已關閉且未合併。 未關閉
難度 2/5 半天 新手友好度 70/100
PolicyEngine/policyengine-sim-api#823 ·
維護者通常 1 天內回覆
-
Integration tests fail due to missing UV virtual environment setup可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉
難度 2/5 1-3 小時 新手友好度 65/100
PolicyEngine/policyengine-sim-api#314 ·
維護者通常 1 天內回覆
-
Update policyengine to 6.10.2可能已有人在做 @policyengine 於 1 天前認領。 未關閉
難度 1/5 1 小時以內 新手友好度 25/100
PolicyEngine/policyengine-sim-api#908 ·
維護者通常 1 天內回覆
-
難度 5/5 一週以上 新手友好度 25/100
PolicyEngine/policyengine-sim-api#907 ·
維護者通常 1 天內回覆
-
Update policyengine to 6.10.1可能已有人在做 @policyengine 於 2 天前認領。 未關閉
難度 1/5 1 小時以內 新手友好度 20/100
PolicyEngine/policyengine-sim-api#905 ·
維護者通常 1 天內回覆
查看 PolicyEngine/policyengine-sim-api 的全部 Issue
相似的 Issue
-
難度 1/5 1 小時以內 新手友好度 72/100
slavakurilyak/awesome-ai-agents#845 ·
維護者通常 1 天內回覆
-
tests: pin that the atomic writers in utils/paths.py stage the temporary file in the target's directory可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉difficulty:2 enhancement good first issue
難度 1/5 1-3 小時 新手友好度 92/100
MakazhanAlpamys/Soup#2178 ·
維護者通常 1 天內回覆
-
[BUG] dcg.waggr permutation p-values are folded twice, so near-zero scores get the smallest p-values未關閉
難度 2/5 1-3 小時 新手友好度 75/100
scverse/rapids-singlecell#854 ·
維護者通常 1 天內回覆
-
Slang input: int8_t4_packed and uint8_t4_packed are copied into CrossGL可能已有人在做 @ninglinLiu 今天認領。 未關閉area:frontend backend:slang bug direction:input
難度 2/5 1-3 小時 新手友好度 70/100
維護者通常 1 天內回覆
-
random_elements(unique=True) on an OrderedDict: ZeroDivisionError once only zero weights remain, AssertionError with use_weighting=False可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉
難度 2/5 1-3 小時 新手友好度 85/100
維護者通常 13 天內回覆