Delegate telemetry and completed Orrery publication to microcosm-local-provider
Maintainers usually reply within 1 day
@anth-volk is already working on this.
Since Oct 8, 2026.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reviewing draft PR #1151 and the proposed provider dependency, then trace the embedded publication and telemetry implementation and its tests. Verify the actual UK graph export, publication-before-HF order, retry behavior, cache path, and versioned database compatibility; ensure the calibration dashboard is unaffected. Draft tests should pin the provider source, while merge readiness depends on the provider dependencies being merged and released and locks regenerated.
Written by the indexing model from the issue text.
Description
Implement and test the adapter now in a draft PR stacked on the minimal publication PR #1151. Defer merge and activation until PolicyEngine/microcosm-local-provider#3 and its predecessor are merged, all required provider distributions are published and registry configuration is verified. Preserve the actual UK graph export, publication-before-HF order, retry policy independent of telemetry runs, cache path and versioned database compatibility. Remove the embedded implementation; do not affect the calibration dashboard. Pin exact provider source for draft tests, then replace with released versions and regenerate locks before merge.
- 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
-
Publish UK Orrery output with a minimal build-service changePossibly taken @anth-volk claimed this today. Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
PolicyEngine/microcosm#1150 ·
Maintainers usually reply within 1 day
All issues in PolicyEngine/microcosm
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NVIDIA/earth2studio#1241 ·
Maintainers usually reply within 3 days
-
docs(types): update the collection binding note now that typed collections shipped in pycubrid 1.9.0Opendocumentation priority: low size: S
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cubrid-lab/sqlalchemy-cubrid#768 ·
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 65/100
ansys/pydpf-core#3547 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OktoLabsAI/okto-pulse#114 ·
Maintainers usually reply within 1 day