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

Measure Stage 12 coordinator preparation and separate metric producers

Abierto
  • ¿Algo no está bien?
#707 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 30/9/2026.

  • #708 de @anth-volk — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, cloud, observability

Línea de trabajo

Start at the Stage 12 coordinator path and trace the interval from coordinator ownership to child-state persistence. Then locate the central stage registry, Cloud Run and Modal identity handling, AI-facing observability documentation, and focused tests. Done means the new operations, child-input attribution, process identity, region attributes, release requirement, and tests all satisfy the acceptance criteria.

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

Descripción

Problem

A production Stage 12 trace contained an unmeasured 38.7-second interval after the coordinator acquired report execution ownership and before it persisted child simulation state. Simulation services also reuse platform identifiers as metric instance identifiers, which can cause Google Monitoring time-series collisions.

Proposed change

  • Measure the full coordinator preparation interval.
  • Add nested registered operations for output planning, country model loading, output configuration, output variable resolution, and baseline/reform child input construction.
  • Emit the normal operation completion logs and duration metrics for each new operation.
  • Give each Cloud Run and Modal Python process a stable unique instance identifier.
  • Populate Cloud Run and Modal region resource attributes.
  • Require the observability package release that supplies process identity.
  • Update AI-facing observability documentation and focused tests.

Acceptance criteria

  • Every new operation name is defined in the central stage registry.
  • The full interval between coordinator ownership and child-state persistence is measured.
  • Child input measurements identify baseline or reform without adding unbounded metric labels.
  • Cloud Run and Modal identity and region behavior is covered by tests.
  • The next deployed Stage 12 run attributes the previously unmeasured interval to the new nested operations.
Lenguaje dominante
Python
Estrellas
1
Forks
1
Merge medio
1 d 1 h
PR fusionados (30 d)
22

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/policyengine-sim-api

Todos los issues de PolicyEngine/policyengine-sim-api

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.