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

CreateNode lifecycle stalls at the validators stage with no verdict — a validator never answers within its window during the platform-startup boot-activity create

Closed
  • Is something wrong?
#6,391 17 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
18/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
csharp
Domain
backend

Research direction

Start with the CreateNode staged-verdict code in MeshWeaver.Mesh.MeshExtensions and the LifecycleVerdictStalledException it throws, to see which validators arm a wait and whether each one posts a terminal verdict. Then check the [PlatformStartup] boot-recording path that creates Admin/PlatformVersion/_Activity/startup-…. The issue leaves the cause open, so 'done' means a confirmed cause and a fix or a documented decision, not just a reproduction.

Written by the indexing model from the issue text.

Description

bug sev:M

What is failing. The CreateNode lifecycle verdict pipeline (MeshWeaver.Mesh.MeshExtensions, category MeshWeaver.Mesh.CreateNode) waits on a staged verdict before committing. For the boot-activity create issued by platform startup (Admin/PlatformVersion/_Activity/startup-380439f5 — the [PlatformStartup] boot recording), no verdict arrived within the 30 s window while the request sat at the validators stage. Nothing refused the request, so a validator either never answered or its answer was lost — the create's fate is unknown, which is why the message tells the reader to re-read the target before retrying.

Probable cause — moderate confidence, not pinned. The evidence (a single log line, no stack into the validator stage) supports a lost-or-never-minted validator verdict rather than a validation failure, but cannot distinguish between the two families that fit:

  • Boot ordering. The node is created during platform startup; a validator whose partition, NodeType activation or cross-hub stream is not yet ready at that instant may simply never post a verdict within the window.
  • Verdict-loss seams of the kind documented for the write path in Reading a Write Verdict — a stage watcher without a completion arm, or the responder being a single-threaded grain activation whose own turn cannot route the verdict round-trip it is waiting on (the silent-deadlock shape also described in Activity Control Plane).

Impact. Single occurrence on one pod in the memex deployment, during a platform boot. What is at stake is the boot-activity audit record: one boot's startup activity may be missing or incomplete, and the node may or may not have landed after the window. No user-facing path is known to be affected. Judged sev:M; a human may re-rule if this recurs across boots or the node is confirmed lost.

Where to look.

  • MeshWeaver.Mesh.MeshExtensions — the CreateNode staged-verdict machinery and LifecycleVerdictStalledException: the stage registry that names validators, what arms (and re-arms) the wait per validator, and whether every validator path posts exactly one terminal even when it completes without emitting.
  • The [PlatformStartup] boot-recording path that creates the Admin/PlatformVersion/_Activity/startup-… node — why a boot-time create runs while validators may not be fully armed, and whether the boot recording survives the stall.
  • Reading a Write Verdict and Activity Control Plane — the documented verdict-loss patterns the validator stage should be checked against.
  • Before retrying or closing: read Admin/PlatformVersion/_Activity/startup-380439f5 to learn whether the node actually landed.
Evidence
Fingerprint 832b105be8c96fa4
Category MeshWeaver.Mesh.CreateNode
Severity Error
Namespace memex
Pods memex-portal-deployment-5f6b9fc9b-hrdhq
Occurrences 1
First seen 2026-10-09 20:36:30Z
Last seen 2026-10-09 20:36:30Z
Routing not determined — no configured route matches the category MeshWeaver.Mesh.CreateNode. 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-09 20:36:30Z memex-portal-deployment-5f6b9fc9b-hrdhq fail: MeshWeaver.Mesh.CreateNode[0]
      [CreateNode] Admin/PlatformVersion/_Activity/startup-380439f5 reached no verdict within 30s — stalled at stage validators
      MeshWeaver.Mesh.MeshExtensions+LifecycleVerdictStalledException: CreateNode of 'Admin/PlatformVersion/_Activity/startup-380439f5' reached no verdict within 30s: it was still waiting at stage 'validators'. Nothing refused the request; whether the stage's own work lands later is unknown, so read the target before retrying.

Opened automatically from Admin/_LogIncident/832b105be8c96fa4. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site f205e0da8dbd21ba: 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
5h 34m
Merged PRs (30d)
960

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.