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

MarkdownView hard-fails rendering text whose backing node was deleted — stale view keeps reading a deleted OnePager comment

Chiusa
  • Qualcosa non va?
#6,129 5 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
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
frontend

Direzione di ricerca

Start by reading the document-loading code in MeshWeaver.Blazor.Components.MarkdownView around the log site named in the issue; the source file is not identified here. Compare the deleted-target behavior with issues #6074 and #6080, and coordinate with the sibling MarkdownEditorView incident. Done means stale saved areas no longer make these views fail on a deleted target; the issue does not identify a test to run.

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

Descrizione

bug sev:L

What is failing

MeshWeaver.Blazor.Components.MarkdownView hard-fails when the node backing its read-only text view no longer exists: a view whose area (Overview/2/ReadOnly/Text) still references MacStudioHighPrivacy/OnePager/_Comment/e99d8732 — a comment node that has since been deleted — reads that path, the read ends with the delete, and the component logs the resulting InvalidOperationException as a failure instead of degrading to a not-found/empty state.

Probable cause — high confidence

Same defect class as #6074 / #6080: a node was deleted while a persisted view area still addressed it, and the view component has no not-found handling for the deleted-target read. Evidence: the failing read is a _Comment child of MacStudioHighPrivacy/OnePager, i.e. a comment removed while a user had the OnePager open; the same burst produced the identical failure one log site over (MarkdownEditorView, sibling incident Admin/_LogIncident/aff49f8e79e3e77c), same deleted path, same pod, same second — both views were reading the same deleted comment from the same open page. #6080 already established that this pod runs the newer delete/read semantics (InvalidOperationException, "read ended with the delete") and that the fix must handle that path as well as the older DeliveryFailureException.

Impact

Nuisance-level: one occurrence, one pod, one user's stale open page erroring until they navigate away or the comment is re-created. No outage, no data loss. The underlying defect class — deleting a node that saved view areas still reference — will keep resurfacing across every view component until the delete flow re-targets saved areas or the view layer degrades gracefully on a missing target.

Where to look

  • MeshWeaver.Blazor.Components.MarkdownView — the document-loading code behind the Loading '{value}' in area '{value}' in Area {path} log site: on a deleted-target read failure, re-read the path / render a not-found or closest-ancestor state instead of failing the view. (The framework source partition is not readable from this triage context, so the component is named by its log category — no file paths invented here.)
  • The delete/merge flow that leaves saved view areas addressing removed paths — the shared root cause; see #6074 and #6080.
  • Coordinate with the sibling MarkdownEditorView incident (Admin/_LogIncident/aff49f8e79e3e77c) — almost certainly one fix covering both components.

Already known

This is the same defect class as #6074 (root cause) and #6080 (same exception path, CollaborativeMarkdownView component) — a human may fold this into that thread, but it adds two more components (MarkdownView, MarkdownEditorView) to the set the fix must cover, plus a third node shape (a _Comment child rather than a top-level document).

Evidence
Fingerprint 87e74696a5d0bcdb
Category MeshWeaver.Blazor.Components.MarkdownView
Severity Error
Exception System.InvalidOperationException
Namespace memex-cloud
Pods memex-portal-deployment-f7664dd89-fnfrt
Occurrences 1
First seen 2026-10-05 08:32:36Z
Last seen 2026-10-05 08:32:36Z
Routing not determined — no configured route matches the category MeshWeaver.Blazor.Components.MarkdownView. 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-05 08:32:36Z memex-portal-deployment-f7664dd89-fnfrt fail: MeshWeaver.Blazor.Components.MarkdownView[0]
      Loading 'text' in area 'Overview/2/ReadOnly/Text' in Area Overview/2/ReadOnly/Text
      System.InvalidOperationException: No node found at 'MacStudioHighPrivacy/OnePager/_Comment/e99d8732': the node was deleted, and this read of it ended with the delete. Read the path again if it is re-created.

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

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.