Measure Stage 12 coordinator preparation and separate metric producers
维护者通常 1 天内回复
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- python
- 领域
- backend, cloud, observability
调研方向
Start at the Stage 12 coordinator path and trace the interval from coordinator ownership to child-state persistence. Then locate the central stage registry, Cloud Run and Modal identity handling, AI-facing observability documentation, and focused tests. Done means the new operations, child-input attribution, process identity, region attributes, release requirement, and tests all satisfy the acceptance criteria.
由索引模型根据 Issue 内容生成。
描述
Problem
A production Stage 12 trace contained an unmeasured 38.7-second interval after the coordinator acquired report execution ownership and before it persisted child simulation state. Simulation services also reuse platform identifiers as metric instance identifiers, which can cause Google Monitoring time-series collisions.
Proposed change
- Measure the full coordinator preparation interval.
- Add nested registered operations for output planning, country model loading, output configuration, output variable resolution, and baseline/reform child input construction.
- Emit the normal operation completion logs and duration metrics for each new operation.
- Give each Cloud Run and Modal Python process a stable unique instance identifier.
- Populate Cloud Run and Modal region resource attributes.
- Require the observability package release that supplies process identity.
- Update AI-facing observability documentation and focused tests.
Acceptance criteria
- Every new operation name is defined in the central stage registry.
- The full interval between coordinator ownership and child-state persistence is measured.
- Child input measurements identify baseline or reform without adding unbounded metric labels.
- Cloud Run and Modal identity and region behavior is covered by tests.
- The next deployed Stage 12 run attributes the previously unmeasured interval to the new nested operations.
- 主要语言
- Python
- 星标
- 1
- 派生
- 1
- 平均合并
- 1 天 6 小时
- 30 天内合并 PR
- 24
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PolicyEngine/policyengine-sim-api 的其他 Issue
-
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.2.7可能已有人在做 @policyengine 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 55/100
PolicyEngine/policyengine-sim-api#745 ·
维护者通常 1 天内回复
-
Expose the certified dataset SHA-256 and gate production on the served identity可能已有人在做 @MaxGhenis 今天认领。 未关闭
难度 4/5 3-5 天 新手友好度 48/100
PolicyEngine/policyengine-sim-api#742 ·
维护者通常 1 天内回复
-
Update policyengine to 6.2.6可能已有人在做 @policyengine 于 1 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 12/100
PolicyEngine/policyengine-sim-api#738 ·
维护者通常 1 天内回复
-
Update policyengine to 6.2.4可能已有人在做 @policyengine 于 2 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 15/100
PolicyEngine/policyengine-sim-api#736 ·
维护者通常 1 天内回复
查看 PolicyEngine/policyengine-sim-api 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
lugassawan/swe-workbench#799 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
vllm-project/vllm#61131 ·
维护者通常 1 天内回复
-
Non-string form field names raise AttributeError when files are attached可能已有人在做 @nightcityblade 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
-
难度 2/5 1-3 小时 新手友好度 78/100
kubernetes-client/python#2735 ·
维护者通常 1 天内回复
-
desktop help wanted test
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复