lock-pinned-digests: the pinned-manifest lock lane is red

Abierto
  • ¿Algo no está bien?
#7,991 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
43/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp, github-actions
Área
ci-cd

Línea de trabajo

Start with the newest ledger entry and open its linked run and failed job logs, especially the Lock every manifest the fleet pins step. Compare its annotations with the earlier failure because the recorded cause changed; the issue does not identify the underlying code or test to change. The work is done when the pinned-manifest lock lane runs green.

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

Descripción

bug ci-lock-pinned-digests-red sev:M

lock-pinned-digests: the pinned-manifest lock lane is red — a lane of Systemorph/MeshWeaver is red. This issue is the ledger: every red run of the lane appends a dated entry below, and the run that goes green again closes it. A red within 7 days of the close REOPENS this issue rather than filing a second one, so one outage is one story.

Each entry is also POSTed, signed, to the control portal's triage inbox (Hosting/PlatformBuilds on control.systemorph.com), whose triage agent opens a thread on it. Read the newest entry first — the failed jobs link straight to their logs.

Ledger

2026-11-08T01:27:36Z — failure — run 42432425142
commit a4fba19acd94e2d2906a70b98d2e096256a2e6e7
trigger schedule
platform set (none)
failed jobs Every pinned manifest is locked — step Lock every manifest the fleet pins — errors 605a7fef0a/2
cause 8c2788c0a1 — first recorded red in this ledger (no earlier entry carries a cause)
2026-11-08T01:48:59Z — failure — run 42432425142
commit a4fba19acd94e2d2906a70b98d2e096256a2e6e7
trigger schedule
platform set (none)
failed jobs Every pinned manifest is locked — step Lock every manifest the fleet pins — errors 38dafc3f8b/2
cause e0847749d0 — 🔀 CHANGED since the previous red (8c2788c0a1) — a different job, step or error text failed this time; read THIS run's annotations, not the earlier diagnosis
Lenguaje dominante
C#
Estrellas
12
Forks
5
Merge medio
5 h 11 min
PR fusionados (30 d)
978

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

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 Systemorph/MeshWeaver

Todos los issues de Systemorph/MeshWeaver

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.