Skip to content

NumberFieldView subscribe to user hub times out — same hub-cache routing failure as issue #1195 #1196

Closed

Description

@meshweaver-cloud

What is failing

MeshWeaver.Blazor.Components.NumberFieldView fails to load the Order field in area Settings/2/2/2/1/5 for user sglauser. A SubscribeRequest sent via hub cache gmIIqhF220CKKxqxgY_J7Q gets no response within 60 seconds, producing System.TimeoutException.

Probable cause (high confidence)

This is not a new defect — it is the same downstream symptom already filed as issue #1195 (also a NumberFieldView timeout, same hub cache, same target user, same pod, same area path). The sibling incident covers 4 occurrences between 22:42 and 04:52; this incident is a 5th occurrence at 05:03 (same request id lineage 8wgRIzmUzUO7AhciaDLkFw). The root cause is a hub-cache/subscribe-routing failure: the target user hub's grain (sglauser) is either not activated, not reachable, or not responding to SubscribeRequest. The MessageHubGrain TimeoutException incident (issue #1186) documents the upstream mechanism — no query provider claims the target hub's partition.

Evidence:

  • Same hub cache id (gmIIqhF220CKKxqxgY_J7Q) across both incidents
  • Same target user (sglauser), same pod (kmwvr), same settings area
  • Same exception message and 60-second timeout duration
  • Timestamps form a continuous sequence (22:42 → 23:57 → 02:53 → 04:52 → 05:03)

Impact

Low. 1 additional occurrence, same pod, same user. The NumberFieldView for the Order setting fails to render during that window. No broader blast radius beyond user sglauser.

Where to look


Evidence

Fingerprint b7b494536110682a
Category MeshWeaver.Blazor.Components.NumberFieldView
Severity Error
Exception System.TimeoutException
Top frame MeshWeaver.Messaging.AccessContextCaptureExtensions.RestoringObserver1.OnError(Exception error)`
Namespace memex-cloud
Pods memex-portal-deployment-59479dc7d9-kmwvr
Occurrences 1
First seen 2026-08-11 05:03:54Z
Last seen 2026-08-11 05:03:54Z
Recent log lines
2026-08-11 05:03:54Z memex-portal-deployment-59479dc7d9-kmwvr fail: MeshWeaver.Blazor.Components.NumberFieldView[0]
      Loading 'Order' in area 'Settings/2/2/2/1/5' in Area Settings/2/2/2/1/5
      System.TimeoutException: No response received in hub cache/gmIIqhF220CKKxqxgY_J7Q within 00:01:00 for request SubscribeRequest (id=8wgRIzmUzUO7AhciaDLkFw) → target sglauser. The request may have been undeliverable or the target hub was not found.
         at System.Reactive.PlatformServices.ExceptionServicesImpl.Rethrow(Exception exception)
         at System.Reactive.ExceptionHelpers.Throw(Exception exception)
         at System.Reactive.Stubs.<>c.<.cctor>b__2_1(Exception ex)
         at System.Reactive.AnonymousSafeObserver`1.OnError(Exception error)
         at System.Reactive.Sink`2.OnError(Exception error)
         at System.Reactive.Sink`2.OnError(Exception error)
         at System.Reactive.Sink`2.OnError(Exception error)
         at System.Reactive.Sink`2.OnError(Exception error)
         at System.Reactive.SafeObserver`1.WrappingSafeObserver.OnError(Exception error)
         at System.Reactive.Sink`2.OnError(Exception error)
         at MeshWeaver.Messaging.AccessContextCaptureExtensions.RestoringObserver`1.OnError(Exception error) in /home/runner/work/MeshWeaver/MeshWeaver/src/MeshWeaver.Messaging.Hub/AccessContextCaptureExtensions.cs:line 174
         at System.Reactive.SafeObserver`1.WrappingSafeObserver.OnError(Exception error)
         at System.Reactive.Linq.ObservableImpl.SelectMany`2.ObservableSelector._.InnerObserver.OnError(Exception error)
         at System.Reactive.ObserverBase`1.OnError(Exception error)
         at System.Reactive.SafeObserver`1.WrappingSafeObserver.OnError(Exception error)
         at System.Reactive.Sink`2.OnError(Exception error)
         at System.Reactive.Subjects.FastImmediateObserver`1.EnsureActive(Int32 count)
         at System.Reactive.Subjects.ReplaySubject`1.ReplayBase.OnError(Exception error)
         at MeshWeaver.Mesh.MeshNodeStreamHandle.TypedContentObserver.OnError(Exception…[truncated]

Opened automatically from Admin/_LogIncident/b7b494536110682a. Recurrences are folded into this issue rather than opening new ones.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions