PodHubNotHereException in PodHubGrain.Deliver

Chiusa
  • Qualcosa non va?
#7,888 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@rbuergi ci sta già lavorando.

Dal 4/11/2026.

  • #7894 di @rbuergi — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
20/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
csharp
Ambito
backend

Direzione di ricerca

The report names PodHubGrain.Deliver as the top frame, but provides no source file, failing test, or reproduction steps. Start by tracing that method and the PodHubNotHereException call path, then inspect the linked pull request #7894 to understand work already underway. Done means the underlying fault is addressed and a test or other evidence shows the exception no longer occurs.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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 3d1afe69530620f6
Category MeshWeaver.Hosting.Orleans.RoutingGrain
Severity Error
Exception MeshWeaver.Connection.Orleans.PodHubNotHereException
Top frame MeshWeaver.Hosting.Orleans.PodHubGrain.Deliver
Namespace memex-cloud 1 occurrence(s), 2026-11-04 14:38:45Z → 2026-11-04 14:38:45Z; pods memex-portal-deployment-5d55dd9969-9s5hh
Occurrences 1
First seen 2026-11-04 14:38:45Z
Last seen 2026-11-04 14:38:45Z
Routing not determined — no configured route matches the category MeshWeaver.Hosting.Orleans.RoutingGrain. 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 14:38:45Z memex-portal-deployment-5d55dd9969-9s5hh

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

This log site's previous ticket, https://github.com/Systemorph/MeshWeaver/issues/7001, 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/3d1afe69530620f6. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site 168d0f4e80a7fec1: other fingerprints of this site fold in here as comments rather than opening tickets of their own.

Lingua principale
C#
Stelle
12
Fork
5
Merge medio
5h 11m
PR unite (30g)
978

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Systemorph/MeshWeaver

Tutte le issue di Systemorph/MeshWeaver

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.