Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Vendor scorecard#183's base-side grid record and apply known gaps in the replay gate

已关闭
#636 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

已经有一个关联 PR 被合并了。

  • #637 来自 @MaxGhenis —— 已合并

评估

难度
4/5
预计耗时
3-5 天
新手友好度
32/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
json, python
领域
testing

调研方向

Start with the vendored replay_receipt.v1.json in policyengine.py and its mirrors, then compare them with scorecard main at 71cad306 to see what the new diff.base_events grid record and the tightened measure-year lists require. Read the replay gate's known-gap logic and the decision record d1344-replay-regressions-v1 before changing it. Done means new receipts validate against the refreshed schema and the known-gap check follows the exact base-side rule, with tests covering inert and missing-and-supported cases.

由索引模型根据 Issue 内容生成。

描述

Follow-up to #634 and #635 (UK replay gate policy d1344-replay-regressions-v1).

policyengine-scorecard#183 merged as 71cad306. Every replay receipt now carries:

  • the comparison base's own grid record, diff.base_events.<event>, with these fields: staging and run manifest digests, supported years, full_supported_grid_complete, and the inert, missing and unsupported measure-years;
  • the candidate's missing_measure_years and unsupported_measure_years lists.

policyengine.py's vendored replay_receipt.v1.json and its mirrors are closed, so every new receipt is refused until they are refreshed.

Work:

  • Vendor the schema from scorecard main at 71cad306. Extend the mirrors, including the tightened measure-year lists: a non-empty measure_key and unique items.
  • Implement the decision record's exact known-gap test. A candidate measure-year that is inert, or missing and supported, is a known gap only if the base's record for the same event lists it as inert, or missing and supported.
主要语言
Python
星标
8
派生
10
平均合并
1 天 2 小时
30 天内合并 PR
51

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

PolicyEngine/policyengine.py 的其他 Issue

查看 PolicyEngine/policyengine.py 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。