Publish UK Orrery output with a minimal build-service change
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading the approaches in issues #1099 and #1144, and compare them with the broader refactor in #1148. Trace UK build completion and the existing Hugging Face artifact and telemetry paths; the payload does not name specific files or tests. Done means graph and receipt files are published with durable retries and included in artifacts, existing telemetry behavior is preserved, and unit plus repository-local integration tests cover the change.
Written by the indexing model from the issue text.
Description
Replace the broad service refactor in #1148 with a minimal implementation based on #1099 and #1144. Automatically export execution graphs at UK build completion, preserve exact public-safe files, queue authenticated immutable publication with durable retries independent of telemetry run IDs, then include graph and receipt files in existing Hugging Face artifacts. Preserve the existing telemetry layout and behavior. Add explicit unit and repository-local integration tests; do not test the hosted runs app from Microcosm. A separate provider change and deferred Microcosm migration will move reusable publication and graph reading to microcosm-local-provider. Calibration-dashboard telemetry reads are out of scope.
- Dominant language
- Python
- Stars
- 0
- Forks
- 5
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 115
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PolicyEngine/microcosm
-
Update two stale comments about the export-mass reviewed-exclusion registerPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
PolicyEngine/microcosm#1108 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
PolicyEngine/microcosm#475 ·
Maintainers usually reply within 1 day
-
Generate complete WIC participation in the ACS local-area buildPossibly taken @anth-volk claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
PolicyEngine/microcosm#1155 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
PolicyEngine/microcosm#1154 ·
Maintainers usually reply within 1 day
-
Delegate telemetry and completed Orrery publication to microcosm-local-providerPossibly taken @anth-volk claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
PolicyEngine/microcosm#1152 ·
Maintainers usually reply within 1 day
All issues in PolicyEngine/microcosm
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
MystenLabs/MemWal#1163 · 2 comments ·
Maintainers usually reply within 1 day
-
infertopics leaves new nodes without a topic when untopiced neighbours outnumber topiced onesPossibly taken @moneebullah25 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ClanGenOfficial/clangen#6254 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FinanceFlash/unvibecode#218 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day