Error in Polly

Cerrado
  • ¿Algo no está bien?
#7,901 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
csharp
Área
observability

Línea de trabajo

The report points to log site f4421ec3d5e5a054 and incident node Admin/_LogIncident/76b8759ba3d9d38a, but gives no source file or reproduction steps. Begin by inspecting that incident on the instance that recorded it and locating the log site in the repository. The report says the triage draft is not published; the expected behavior and a way to verify it are not specified.

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 76b8759ba3d9d38a
Category Polly
Severity Error
Namespace memex-cloud 1 occurrence(s), 2026-11-05 01:49:12Z → 2026-11-05 01:49:12Z; pods memex-portal-deployment-857c488df7-pz6mj
Occurrences 1
First seen 2026-11-05 01:49:12Z
Last seen 2026-11-05 01:49:12Z
Routing not determined — no configured route matches the category Polly. 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-05 01:49:12Z memex-portal-deployment-857c488df7-pz6mj

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

Opened automatically from Admin/_LogIncident/76b8759ba3d9d38a. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site f4421ec3d5e5a054: 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.