PodHubNotHereException in PodHubGrain.Deliver

Closed
  • Is something wrong?
#7,888 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@rbuergi is already working on this.

Since Nov 4, 2026.

  • #7894 by @rbuergi — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
backend

Research direction

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.

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 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.

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.