Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

NamedAreaView Overview render under ClaimsDeepfield fails for user 'rsalzmann': the partition's read stream ended and every area view reports a Read denial

Aperta
  • Qualcosa non va?
#7,720 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
authentication, backend

Direzione di ricerca

Start with MeshWeaver.Blazor.Components.NamedAreaView, then trace the standing-read follow through DeclaredPointRead, RevisionAdmission.AdmitEachRevision, and ClientSubscriptionReadAdmission. Compare current whoami or GetEffectivePermissions results with the partition's _Access/_Policy and the access-commit feed around 08:14:17Z; the issue does not establish which cause is correct. Done means identifying whether this is a correct denial or a false/partition-state denial, and explaining the empty area name.

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

Descrizione

bug sev:M

Observed

The Blazor component MeshWeaver.Blazor.Components.NamedAreaView logged its "Error in control stream for area …" failure repeatedly on one page render, every line carrying the same System.InvalidOperationException: access denied for user rsalzmann, lacking Read on ClaimsDeepfield, because "the read stream DKMK0f-ExUKVoqNnf5PvHg served has ended (revoked, expired, or no longer admitted)".

What the samples show beyond the footer's raw lines:

  • One underlying stream end, fanned out per area element. The same stream id DKMK0f-ExUKVoqNnf5PvHg appears in every line, and the area names enumerate one layout tree ({path}, …{path}, …{path}, …{path}), emitted within fractions of a millisecond of each other — one render pass of the Overview area under the ClaimsDeepfield partition, not independent failures.
  • The refusal names the partition ROOT. The path lacking Read is ClaimsDeepfield itself, not a node under it — consistent with the scope chain denying at the partition root.
  • The final sampled line, ~3 s after the burst, carries an EMPTY area name ("Error in control stream for area " with nothing after it) — either an area whose name did not resolve or the log call not formatting it.
  • The partition has a history. Ops log entry {path} (2026-10-06, [InstallCompleteness]) records that ClaimsDeepfield is an UNINSTALLED package whose install record survived: the partition was deleted and its root re-created 2026-09-05, with none of the other 82 declared nodes present (MeshWeaver#4812). The partition exists today as a bare re-created root.
  • The caller's token record {path} was last written ~11 s after the burst; whether that is connected is not established.

Where and when

One namespace (memex-cloud), one pod, one user, one ~3-second window on 2026-10-31 (burst at 08:14:17Z, last line 08:14:20Z). No other pod, user or partition appears in the incident.

Impact

One signed-in user's view of the Overview page under ClaimsDeepfield failed, on one instance. If the stream end was a false denial, the same shape could deny other viewers of that partition; nothing in the incident shows that it did.

Not established

  • Why the read stream ended. "Revoked, expired, or no longer admitted" are the three causes the message itself names, and the evidence does not separate them.
  • Whether rsalzmann still holds Read on ClaimsDeepfield now, and whether a fresh page load renders or refuses.
  • Whether the denial is the correct outcome of a partition that is an orphaned, bare re-created root, or a false denial from the read-follow machinery.
  • What produced the empty area name in the last line.

Candidate causes and the reading that separates them

  1. A settled, correct denial. rsalzmann holds no grant on the re-created ClaimsDeepfield partition — its _Access/_Policy were not re-created with the root, or an entitlement for the package expired or was revoked — and a page or subscription admitted before that change was ended by the standing-read follow. Predicts: {path} and {path} are absent or carry no grant naming rsalzmann (or Public); a fresh page load refuses with the same denial; the {path} history for the package shows an expiry or retraction at or before 08:14Z.
  2. A transient false denial. The follow's re-check on an access commit elsewhere (any grant, membership or role change, or a declared feed gap) withdrew the standing verdict, and the re-check had not settled when the view read it — the documented "no access for the length of one re-check" window surfacing as a hard refusal. Predicts: rsalzmann holds a valid grant now; a reload renders; the access-commit feed on memex-cloud around 08:14:17Z shows a commit that does not change this user's rights on ClaimsDeepfield.
  3. "No longer admitted" by a partition-state change. A change to the partition itself ({path} of the package, a root or _Policy rewrite, an ownership change) ended the admission rather than revoking a grant. Predicts: a partition-level change to ClaimsDeepfield in the minutes before 08:14:17Z, visible in the partition's version history and the plugin registry.

The single reading that separates all three: what whoami / GetEffectivePermissions answers for rsalzmann at ClaimsDeepfield now, read against {path} and _Policy and the access-commit feed at 08:14:17Z.

Where to look

  • MeshWeaver.Blazor.Components.NamedAreaView — the log site; the fan-out shape (one stream end reported once per area element of one render) and the empty area name in the final line are both visible there.
  • The standing-read follow machinery that ends streams with exactly this message: DeclaredPointRead / RevisionAdmission.AdmitEachRevision / ClientSubscriptionReadAdmission (MeshWeaver.Data, MeshWeaver.Graph), documented in Access Control Architecture → "An open subscription ends with the read".
  • {path} — the [InstallCompleteness] record that ClaimsDeepfield is an uninstalled package with a surviving install record (MeshWeaver#4812).
  • {path} — the caller's token record, written ~11 s after the burst.
Evidence
Fingerprint 6e20864fb3b4d577
Category MeshWeaver.Blazor.Components.NamedAreaView
Severity Error
Exception System.InvalidOperationException
Namespace memex-cloud 24 occurrence(s), 2026-10-31 08:14:17Z → 2026-10-31 08:14:20Z; pods memex-portal-deployment-68b656cd88-thr49
Occurrences 24
First seen 2026-10-31 08:14:17Z
Last seen 2026-10-31 08:14:20Z
Routing not determined — no configured route matches the category MeshWeaver.Blazor.Components.NamedAreaView. 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 log lines 
2026-10-31 08:14:17Z memex-portal-deployment-68b656cd88-thr49 fail: MeshWeaver.Blazor.Components.NamedAreaView[0]
      Error in control stream for area {path}
      System.InvalidOperationException: Access denied: user 'rsalzmann' lacks Read permission on 'ClaimsDeepfield' — the read stream DKMK0f-ExUKVoqNnf5PvHg served has ended (revoked, expired, or no longer admitted)
2026-10-31 08:14:17Z memex-portal-deployment-68b656cd88-thr49 fail: MeshWeaver.Blazor.Components.NamedAreaView[0]
      Error in control stream for area {path}
      System.InvalidOperationException: Access denied: user 'rsalzmann' lacks Read permission on 'ClaimsDeepfield' — the read stream DKMK0f-ExUKVoqNnf5PvHg served has ended (revoked, expired, or no longer admitted)
2026-10-31 08:14:17Z memex-portal-deployment-68b656cd88-thr49 fail: MeshWeaver.Blazor.Components.NamedAreaView[0]
      Error in control stream for area {path}
      System.InvalidOperationException: Access denied: user 'rsalzmann' lacks Read permission on 'ClaimsDeepfield' — the read stream DKMK0f-ExUKVoqNnf5PvHg served has ended (revoked, expired, or no longer admitted)
2026-10-31 08:14:17Z memex-portal-deployment-68b656cd88-thr49 fail: MeshWeaver.Blazor.Components.NamedAreaView[0]
      Error in control stream for area {path}
      System.InvalidOperationException: Access denied: user 'rsalzmann' lacks Read permission on 'ClaimsDeepfield' — the read stream DKMK0f-ExUKVoqNnf5PvHg served has ended (revoked, expired, or no longer admitted)
2026-10-31 08:14:20Z memex-portal-deployment-68b656cd88-thr49 fail: MeshWeaver.Blazor.Components.NamedAreaView[0]
      Error in control stream for area 
      System.InvalidOperationException: Access denied: user 'rsalzmann' lacks Read permission on 'ClaimsDeepfield' — the read stream DKMK0f-ExUKVoqNnf5PvHg served has ended (revoked, expired, or no longer admitted)

Opened automatically from Admin/_LogIncident/6e20864fb3b4d577. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site b15ff3cea75eb4fe: 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 28m
PR unite (30g)
976

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.