Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

ActivationRecycle refuses five existing Doc NodeTypes as unknown (memex portal pod)

Abierto
  • ¿Algo no está bien?
#6,826 10 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Ya se ha fusionado un pull request relacionado.

  • #6872 de @rbuergi — fusionado

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp, postgresql
Área
backend, observability

Línea de trabajo

Start in src/MeshWeaver.Graph/Configuration/ActivationRecycle.cs, at Request and TypeExists, to see how the type-existence query is run and how its failure or timeout is reported. Then check NodeTypeRecycleCascade, which issues the per-type requests, and the QueryProviderStalledException logs under Admin/_LogIncident for 2026-10-15. Done means the cause of the false "unknown NodeType" answer is identified and a re-issued request for one of the five types succeeds.

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

Descripción

bug sev:M

Observed

Five activation-recycle requests, one per NodeType, were refused with unknown NodeType(s) and nothing recycled, logged by MeshWeaver.Graph.Configuration.NodeTypeRecycleCascade as "the activation recycle for {path} was REFUSED". The five types are Doc/Architecture/ATypicalNodeType/Budget, Doc/Architecture/BusinessRules/Cession, Doc/DataMesh/PythonPandasNode/PandasExplorer, Doc/DataMesh/SocialMedia/Post, Doc/DataMesh/SocialMedia/Profile — and all five exist: each is a live, compiled NodeType node with compilationStatus Ok (e.g. Doc/Architecture/ATypicalNodeType/Budget last compiled at v94, release 20261008225416-I2aihU-U).

The refusal string belongs to ActivationRecycle.Request (src/MeshWeaver.Graph/Configuration/ActivationRecycle.cs): its type-existence check TypeExists — FindStaticNode for framework types, otherwise a System mesh query path:{type} filtered to nodeType:NodeType under a 30 s ReadBudget — answered "not found" for each type. Consistent with a refused request writing nothing: no node under Admin/_Recycle names any of the five types (the request records that do exist there — recycle-mcp-* — all name other types and carry per-process reports).

The five refusals arrived in one burst, ~30–180 ms apart, all on the one portal pod — the shape of a single NodeTypeRecycleCascade enumerating its dependency network and calling ActivationRecycle.Request once per type, not of five independent requests.

Where and when

One pod, namespace memex-cloud, one burst; no other pod logged this shape. Two things it coincides with (both read from the mesh, not the incident):

  • 31 minutes before the burst, the served view of the entire Doc partition was rewritten in one instant — every sampled Doc node (Markdown, NodeType, Code, instance) carries version 2 at 2026-10-15T12:45:05–06Z, including all five refused types' definitions. The definitions' own version history ends earlier (Budget v96 at 2026-10-08T23:52Z); the relationship between that rewrite and the durable history was not established.
  • The same log site recorded a large burst of QueryProviderStalledException incidents earlier the same day (00:49–00:51Z, PostgreSQL partition query providers stalling) — the same component's queries against PostgreSQL partitions had stalled on this namespace within hours of this refusal.

Impact

The activation recycle for these five types did not happen: their live activations keep the build they were born with (StaleStateUntilRecycle) until recycled by hand. Nothing was torn down and nothing was corrupted; the failure is loud and its volume is low (one burst, one pod).

Not established

  • Why TypeExists answered unknown for types that exist — the cause is not established.
  • What initiated the cascade/recycle at that moment: no Admin/_Recycle request names these types, and the newest recycle jobs found for them date from 2026-10-07.
  • Whether the refusals repeat (only one burst observed) or whether other Doc-defined types were refused on other pods.
  • Whether the 12:45 Doc-partition rewrite is connected.

Candidate causes and the reading that separates them

  1. The type-existence query failed or timed out on the issuing pod (ReadBudget, 30 s) and the failure surfaced as "unknown" — consistent with the same site's QueryProviderStalledException bursts hours earlier. Predicts: the durable NodeType rows were present throughout; a request re-issued after the provider recovers succeeds. Reading: re-issue one request (e.g. for Doc/DataMesh/SocialMedia/Post) and see whether it succeeds now; read the pod's PostgreSQL provider health/logs at the burst instant for a stall or timeout.
  2. The 12:45 wholesale rewrite of the Doc partition left the definitions temporarily unreadable (mid-rewrite/import window) and the burst fell inside or just after it. Predicts: refusals cluster only in that window; a path:Doc/Architecture/ATypicalNodeType/Budget query at 13:16 would have returned nothing while the same query now returns the node. Reading: identify what wrote the Doc partition at 12:45 (import/restore/reseed job logs) and whether its window covered 13:16.
  3. The types were genuinely absent from that pod's view (partition not loaded, definitions not activated on the portal pod). Predicts: every activation recycle of Doc-defined types from that pod fails, not just this burst — but the build queue's recycle jobs for these exact types succeeded on 2026-10-07, so this requires something to have changed since. Reading: whether any successful Doc-type activation recycle ran from that pod after 12:45 today.

Where to look

  • src/MeshWeaver.Graph/Configuration/ActivationRecycle.cs — Request / TypeExists (the refusal string and the type-existence check whose answer was wrong).
  • NodeTypeRecycleCascade (MeshWeaver.Graph.Configuration) — the caller that enumerates the cascade network and issues the per-type requests; Doc/WhatsNew/2026-09-18-recycling-a-node-type-now-recycles-everything-built-on-it and Doc/Architecture/StaleStateUntilRecycle ("Recycling a type") describe both halves.
  • Related, same site, same day: the QueryProviderStalledException incidents under Admin/_LogIncident (2026-10-15 00:49–00:51Z).
  • Background: ActivationRecycle landed in Systemorph/MeshWeaver#6054 ("ActivationRecycle: recycle a NodeType's live activations on every process", merged 2026-10-04); its review noted the type-existence check runs as a System mesh query per named type.
Evidence
Fingerprint 117d0db64e11db29
Category MeshWeaver.Graph.Configuration.NodeTypeRecycleCascade
Severity Error
Namespace memex-cloud
Pods memex-portal-deployment-7b96957ddb-pvfvx
Occurrences 5
First seen 2026-10-15 13:16:08Z
Last seen 2026-10-15 13:16:09Z
Routing not determined — no configured route matches the category MeshWeaver.Graph.Configuration.NodeTypeRecycleCascade. 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-15 13:16:08Z memex-portal-deployment-7b96957ddb-pvfvx fail: MeshWeaver.Graph.Configuration.NodeTypeRecycleCascade[0]
      [RecycleCascade] Doc/Architecture/ATypicalNodeType/Budget: the activation recycle for Doc/Architecture/ATypicalNodeType/Budget was REFUSED (unknown NodeType(s): Doc/Architecture/ATypicalNodeType/Budget — nothing was recycled) — no live activation of the type or its dependents was recycled; each keeps the build it was born with until recycled by hand
2026-10-15 13:16:08Z memex-portal-deployment-7b96957ddb-pvfvx fail: MeshWeaver.Graph.Configuration.NodeTypeRecycleCascade[0]
      [RecycleCascade] Doc/Architecture/BusinessRules/Cession: the activation recycle for Doc/Architecture/BusinessRules/Cession was REFUSED (unknown NodeType(s): Doc/Architecture/BusinessRules/Cession — nothing was recycled) — no live activation of the type or its dependents was recycled; each keeps the build it was born with until recycled by hand
2026-10-15 13:16:09Z memex-portal-deployment-7b96957ddb-pvfvx fail: MeshWeaver.Graph.Configuration.NodeTypeRecycleCascade[0]
      [RecycleCascade] Doc/DataMesh/PythonPandasNode/PandasExplorer: the activation recycle for Doc/DataMesh/PythonPandasNode/PandasExplorer was REFUSED (unknown NodeType(s): Doc/DataMesh/PythonPandasNode/PandasExplorer — nothing was recycled) — no live activation of the type or its dependents was recycled; each keeps the build it was born with until recycled by hand
2026-10-15 13:16:09Z memex-portal-deployment-7b96957ddb-pvfvx fail: MeshWeaver.Graph.Configuration.NodeTypeRecycleCascade[0]
      [RecycleCascade] Doc/DataMesh/SocialMedia/Post: the activation recycle for Doc/DataMesh/SocialMedia/Post was REFUSED (unknown NodeType(s): Doc/DataMesh/SocialMedia/Post — nothing was recycled) — no live activation of the type or its dependents was recycled; each keeps the build it was born with until recycled by hand
2026-10-15 13:16:09Z memex-portal-deployment-7b96957ddb-pvfvx fail: MeshWeaver.Graph.Configuration.NodeTypeRecycleCascade[0]
      [RecycleCascade] Doc/DataMesh/SocialMedia/Profile: the activation recycle for Doc/DataMesh/SocialMedia/Profile was REFUSED (unknown NodeType(s): Doc/DataMesh/SocialMedia/Profile — nothing was recycled) — no live activation of the type or its dependents was recycled; each keeps the build it was born with until recycled by hand

Opened automatically from Admin/_LogIncident/117d0db64e11db29. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site 3fa2d9a39770265f: 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 51 min
PR fusionados (30 d)
970

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.