FeedbackHandover watcher errors on a Feedback/Feedback node whose content is MarkdownContent — the content type does not match the NodeType's declared FeedbackContent

Cerrado
  • ¿Algo no está bien?
#6,232 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp
Área
backend

Línea de trabajo

Start in Feedback/Feedback/Source/FeedbackHandover and read the HandOverOnActivation subscription, especially the ContentAs<FeedbackContent> call after the NodeType guard. Then inspect the Feedback/Feedback NodeType declaration and the path that allowed the affected node to retain MarkdownContent. The issue leaves open which side should own the fix; done means mismatched content is handled appropriately and valid feedback still reaches triage or the shared Inbox.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug sev:M

What is failing

The hand-over watcher compiled into the Feedback/Feedback NodeType assumes every node of that type carries FeedbackContent. The node rbuergi/Feedback/20260921-0930-iconcontrol-and-labelcontrol-withcolor-are-bound-by-no-view has NodeType Feedback/Feedback but its content is MarkdownContent (MeshWeaver.Markdown), so ContentAs<FeedbackContent> fails on every hub activation and the watcher logs it at Error level. A node in this state is silently skipped by the watcher — it can never be handed to triage nor relocated to the shared Inbox.

Probable cause

The affected node was originally created under an undeclared nodeType (Feedback) and later re-typed to Feedback/Feedback (the node's own body documents this correction), but its content was never converted — leaving the store holding a node whose content type does not match its NodeType's declared WithContentType<FeedbackContent>(). Two gaps share the blame: (1) create/re-type did not refuse or correct a content-type mismatch against the NodeType's declared content type, and (2) the watcher in HandOverOnActivation treats a non-convertible content as an Error-level event rather than a benign skip. Confidence: high on the mechanism (both the NodeType configuration and the watcher source were read directly in the mesh); medium on which side should own the fix.

Impact

Judged from the numbers this is low: one occurrence on one pod, one affected node, which is a historical bug-report note rather than a live submission — no data is lost and the hand-over pipeline keeps working for correctly-typed nodes. The latent risk is that any submission that lands in this state is silently dropped from the hand-over with only a log line.

Where to look

  • Feedback/Feedback/Source/FeedbackHandover — the HandOverOnActivation subscription: node.ContentAs<FeedbackContent>(hub.JsonSerializerOptions, logger) after the NodeType == "Feedback/Feedback" guard.
  • The NodeType declaration Feedback/Feedback (config.WithContentType<FeedbackContent>().HandOverOnActivation()), and whatever path allowed a node typed Feedback/Feedback to hold MarkdownContent.
  • The affected node itself, whose content $type is MarkdownContent.
Evidence
Fingerprint 8bb81a6bc18d8374
Category FeedbackHandover
Severity Error
Namespace memex
Pods memex-portal-deployment-8669548545-6499s
Occurrences 1
First seen 2026-10-07 07:06:46Z
Last seen 2026-10-07 07:06:46Z
Routing not determined — no configured route matches the category FeedbackHandover. 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-07 07:06:46Z memex-portal-deployment-8669548545-6499s fail: FeedbackHandover[0]
      As<FeedbackContent> for rbuergi/Feedback/20260921-0930-iconcontrol-and-labelcontrol-withcolor-are-bound-by-no-view: value is MeshWeaver.Markdown.MarkdownContent (MeshWeaver.Markdown), not convertible

Opened automatically from Admin/_LogIncident/8bb81a6bc18d8374. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site ab39bcb709b9b7f5: other fingerprints of this site fold in here as comments rather than opening tickets of their own.

Lenguaje dominante
C#
Estrellas
12
Forks
5
Merge medio
5 h 10 min
PR fusionados (30 d)
980

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Systemorph/MeshWeaver

Todos los issues de Systemorph/MeshWeaver

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.