Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

CollaborativeMarkdownView hard-fails when its target document node was deleted — read ends with the delete (stale Hardware/Workstations)

Closed
  • Is something wrong?
#6,080 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
frontend

Research direction

Start in MeshWeaver.Portal.Components.CollaborativeMarkdownView at the document-loading code behind the “Loading document … in Area …” log site, then read the delete/merge flow and issue #6074. Reproduce with the persisted Overview/2/1/2 area targeting Hardware/Workstations; done means the view degrades to a not-found or closest-ancestor state for both the InvalidOperationException and DeliveryFailureException paths.

Written by the indexing model from the issue text.

Description

bug sev:L

What is failing

CollaborativeMarkdownView hard-fails when it loads a document whose node no longer exists: the view reads the node addressed by a saved view area (Overview/2/1/2), the node at that path (Hardware/Workstations) has been deleted, and the read ends with the delete — the component logs the resulting InvalidOperationException as a failure instead of degrading to a not-found/empty state.

Probable cause — high confidence

A saved view area still references a deleted path — the same defect class as #6074 (opened earlier today from the 08:55:40Z burst, missing node Hardware/SamuelGlauserMacBookAir). Evidence:

  • Hardware/Workstations no longer exists in the Hardware partition — no node, no version history.
  • The failing area is the very same Overview/2/1/2 document area #6074 identified as persisting the earlier deleted path.
  • The exception differs from the earlier burst (InvalidOperationException with the "read ended with the delete" message, instead of DeliveryFailureException): this pod runs the newer delete/read semantics, but the view still has no not-found handling, so the defect surfaces either way. Any fix must cover both failure modes.

Impact

Nuisance-level: one occurrence, one pod, one user's stale view erroring until they navigate away or the node is re-created. No outage. The underlying defect class — deleting a node that saved view areas still reference — will keep reproducing across every view component (six sibling incidents earlier today) until the delete flow re-targets saved areas or the view layer degrades gracefully on a missing target.

Where to look

  • MeshWeaver.Portal.Components.CollaborativeMarkdownView — the document-loading code behind the Loading document … in Area … 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 delete/merge flow that leaves saved view areas (Overview/2/1/2) addressing removed paths — the shared root cause; see #6074.
  • Concrete case: deleted Hardware/Workstations in the memex namespace, loaded via the persisted Overview/2/1/2 area.

Already known

This is a recurrence of #6074 (root cause) at the same log site as #6076 (already marked a duplicate of #6074). A human can likely close this against #6074 in seconds, but it adds a second deleted node (Hardware/Workstations) and the newer InvalidOperationException read path — worth folding in as evidence that the fix must handle the read-ended-with-delete case as well as delivery failures.

Evidence
Fingerprint 15ee5966f4305691
Category MeshWeaver.Blazor.Components.CollaborativeMarkdownView
Severity Error
Exception System.InvalidOperationException
Namespace memex
Pods memex-portal-deployment-6dbcd749fb-ps2xz
Occurrences 1
First seen 2026-10-04 09:49:01Z
Last seen 2026-10-04 09:49:01Z
Routing not determined — no configured route matches the category MeshWeaver.Blazor.Components.CollaborativeMarkdownView. 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-04 09:49:01Z memex-portal-deployment-6dbcd749fb-ps2xz fail: MeshWeaver.Blazor.Components.CollaborativeMarkdownView[0]
      Loading document Hardware/Workstations in Area Overview/2/1/2
      System.InvalidOperationException: No node found at 'Hardware/Workstations': 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/15ee5966f4305691. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site 1394b0ddc003f656: 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
3h 59m
Merged PRs (30d)
975

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.