Error in Messaging.MessageService

Cerrado
  • ¿Algo no está bien?
#7,893 9 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
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 at Admin/_LogIncident/6d22019b310ef549 on the instance that recorded the incident and inspect the raw log lines for the single occurrence in MeshWeaver.Messaging.MessageService. The write-up says the triage draft is not published (LogWatch:PublishTriageDraft=false), but it does not identify the fault or the code to change. Determine the cause and expected fix before work can be considered done.

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

Descripción

bug sev:L

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 6d22019b310ef549
Category MeshWeaver.Messaging.MessageService
Severity Error
Namespace memex 1 occurrence(s), 2026-11-04 20:45:49Z → 2026-11-04 20:45:49Z; pods memex-portal-deployment-67cf6d965c-8dwp7
Occurrences 1
First seen 2026-11-04 20:45:49Z
Last seen 2026-11-04 20:45:49Z
Routing not determined — no configured route matches the category MeshWeaver.Messaging.MessageService. 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-11-04 20:45:49Z memex-portal-deployment-67cf6d965c-8dwp7

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

Opened automatically from Admin/_LogIncident/6d22019b310ef549. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site 68a7699745069b20: 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 10 min
PR fusionados (30 d)
981

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.