Critical in LogWatcher.Pipeline

Abierto
  • ¿Algo no está bien?
#7,956 1 comentario 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
3-5 días
Aptitud para principiantes
20/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
csharp
Área
backend

Línea de trabajo

Start by locating the MeshWeaver.LogWatcher.Pipeline logger and the code that reads log lines for triage. The issue says the triage text is not published because LogWatch:PublishTriageDraft=false, but gives no file, test, or expected change. Determine how that setting and incident-node publishing are intended to work; done means the triage write-up reaches the intended destination without publishing raw log lines.

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

Descripción

bug sev:M

The triage write-up stays on the incident node: the agent reads the raw log lines, so its text is not published (LogWatch:PublishTriageDraft=false).

Evidence
Fingerprint log-window-skipped-memex-cloud
Category MeshWeaver.LogWatcher.Pipeline
Severity Critical
Namespace memex-cloud 1 occurrence(s), 2026-11-07 01:18:06Z → 2026-11-07 01:18:51Z; pods
Occurrences 2
First seen 2026-09-27 11:02:50Z
Last seen 2026-11-07 01:18:51Z
Routing not determined — no configured route matches the category MeshWeaver.LogWatcher.Pipeline. This repository is the configured fallback, not a finding about who owns the fault; the category names the LOGGER, which may not be the subject.
Recent sightings
Logged at Pod
2026-09-27 11:03:19Z -
2026-11-07 01:18:51Z -

The log lines themselves are not published: formatted log text can carry the values a call site logged. They stay on Admin/_LogIncident/log-window-skipped-memex-cloud on the instance that recorded them.

This log site's previous ticket, https://github.com/Systemorph/MeshWeaver/issues/7043, was closed about a different fingerprint, and this fault fired after that close. It is left closed: an occurrence of this fingerprint is no evidence that the fault it was closed for came back. This issue now tracks the log site, and later fingerprints of it fold in here.

Opened automatically from Admin/_LogIncident/log-window-skipped-memex-cloud. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site df7022d82cca1b39: other fingerprints of this site fold in here as comments rather than opening tickets of their own.

Lenguaje dominante
C#
Estrellas
12
Forks
5
Merge medio
5 h 14 min
PR fusionados (30 d)
957

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.