Error in Polly

Closed
#7,901 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
csharp
Domain
observability

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
C#
Stars
12
Forks
5
Avg merge
5h 10m
Merged PRs (30d)
981

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Systemorph/MeshWeaver

All issues in Systemorph/MeshWeaver

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.