Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Certify Microcosm builds published side by side in their own release folders

オープン
  • 何か問題がありますか？
#682 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@anth-volk がすでに取り組んでいます。

2026年10月20日 から。

  • #683 @anth-volk による — オープン

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
停滞
技術スタック
python
領域
backend

調査の方向性

Start with the certification and import-time compatibility checks that use release_build_id, then trace manifest parsing and dataset artifact paths. Compare the existing cut_tag behavior with the microcosm_emitter_interface.releases format referenced in the issue. Done means string-valued release and build manifests certify files under their release folder, imports reject mismatched release or build names, and older manifests retain their current behavior.

索引モデルが issue の本文から書いたものです。

説明

Problem

Microcosm is moving its dataset repositories to a new publication layout:

  • each build is published once, in its own folder, releases/<release>/<build>/, and that folder never changes afterwards;
  • one releases.json at the repository root records which build of each release is current;
  • no new Hugging Face tags are created;
  • each build's release_manifest.json names its release and build as two strings (the build is the attempt ID Microcosm already assigns, for example uk-frs-calibration-attempt-20261019T083323Z-6cba5d71), and no longer carries cut_tag.

The format of releases.json and the publication checks are in microcosm-emitter#24 (microcosm_emitter_interface.releases). Microcosm switches to the layout in a later change, after a one-time migration of the existing UK builds.

Certification and the import-time compatibility check currently name a data build with release_build_id, which prefers build.cut_tag (#615). They also assume build is an object. A manifest in the new layout:

  • would fail to parse, because its build is a string;
  • has no tag to pin, so a certificate has to pin the build by its folder path instead;
  • keeps its files inside the build folder, while today's dataset artifact paths are relative to the repository root.

Proposed change

  • Parse a manifest whose release and build are strings, and name its build by build, so two builds of one release never match.
  • Certify such a build from its own folder: the manifest URI must be releases/<release>/<build>/release_manifest.json, and the build's files are pinned at releases/<release>/<build>/<file> at the revision the manifest was certified at.
  • At import, refuse a remote manifest that names a different release or build than the folder it was read from.
  • Keep manifests published before the layout (with cut_tag) behaving exactly as they do now.

Relates to #553 and #615.

主要言語
Python
スター
8
フォーク
10
平均マージ
1日 2時間
マージ済み PR（30日）
50

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

PolicyEngine/policyengine.py のほかの issue

PolicyEngine/policyengine.py の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。