Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Orrery publication doc still names the closed calibration-diagnostics#208 as a prerequisite

Abierto
#1,402 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@anth-volk ya está trabajando en esto.

Desde el 26/10/2026.

  • #1403 de @anth-volk — abierto

Evaluación

Dificultad
1/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
25/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
markdown, python

Línea de trabajo

Read docs/orrery-publication.md and compare its prerequisite claims with the current publication flow described in the issue. Explain that builds submit graph files to the collector’s artifact intake, the collector’s graph worker publishes them, and queued uploads remain pending with files preserved until that path is available. Remove the reference to #208; done when the doc describes today’s behavior and replacement flow without naming #208 as a prerequisite.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

docs/orrery-publication.md says remote Orrery publication "requires PolicyEngine/calibration-diagnostics#208 deployed", and that the hosted authorization deployment remains a prerequisite after migrating a workstation. #208 was closed unmerged on 2026-10-15, so it will never be deployed.

The collector will publish Orrery graph files itself instead: builds submit them to the collector's artifact intake (PolicyEngine/microcosm-collector#12), and the collector's graph worker builds and publishes them. Until then, uploads that builds queue stay pending in the emitter's local queue with their files preserved, and no attempt can succeed.

The doc should:

  • describe what happens today and what replaces the direct upload;
  • stop naming #208 as a prerequisite.
Lenguaje dominante
Python
Estrellas
0
Forks
6
Merge medio
1 d 20 h
PR fusionados (30 d)
133

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de PolicyEngine/microcosm

Todos los issues de PolicyEngine/microcosm

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.