From 5df0fb64f5224bebb153a676fc2fb7efd994a8c9 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 11:52:23 +0100 Subject: [PATCH] mesh-build-go: a finding writer that cannot start is said, and the module serves on (A-394) Live on shanks the bundle exited 39 times on 'an ordered consumer of mesh-conditions.findings-asked: context deadline exceeded', so the seat node-build-go never answered steps and the seed waited. Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- modules/mesh-build-go/cmd/mesh-build-go/main.go | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/modules/mesh-build-go/cmd/mesh-build-go/main.go b/modules/mesh-build-go/cmd/mesh-build-go/main.go index 1c404a996..7886aaca6 100644 --- a/modules/mesh-build-go/cmd/mesh-build-go/main.go +++ b/modules/mesh-build-go/cmd/mesh-build-go/main.go @@ -87,8 +87,9 @@ func main() { go func() { <-stdio.Served() if err := findings.Start(ctx); err != nil { - logf("the finding writer: %v", err) - os.Exit(1) + // Said, and the module goes on serving: a finding writer that cannot hear its asks keeps its findings + // in its state alone, as the indexer does (lead answer A-394); its builds and steps never wait on it. + logf("the finding writer cannot start, its findings are kept in the state alone: %v", err) } }() }