ruvnet/ruflo · error · Error

GNN bridge not initialized

Error message

GNN bridge not initialized

What it means

GNNBridge.loadGraph() found this.initialized still false — initialize() (WASM load or fallback setup) has not completed. The load is refused before mutating the node/edge stores; every public bridge method carries the same readiness guard.

Source

Thrown at v3/plugins/healthcare-clinical/src/bridges/gnn-bridge.ts:387

      } else {
        this.logger.warn('WASM module not available, using fallback implementation');
      }

      this.initialized = true;
    } catch (error) {
      this.logger.warn('Failed to initialize WASM, using fallback', {
        error: error instanceof Error ? error.message : String(error),
      });
      this.initialized = true;
    }
  }

  /**
   * Load a graph into the GNN
   */
  async loadGraph(nodes: GNNNode[], edges: GNNEdge[]): Promise<void> {
    if (!this.initialized) {
      throw new Error('GNN bridge not initialized');
    }

    // Clear existing graph
    this.nodes.clear();
    this.edges = [];
    this.nodeIdToIndex.clear();

    // Index nodes
    let idx = 0;
    for (const node of nodes) {
      this.nodes.set(node.id, node);
      this.nodeIdToIndex.set(node.id, idx++);
    }

    // Store edges
    this.edges = edges;

    if (this.wasmModule) {

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Ensure the module/bridge/plugin initialize() method has been called and awaited before invoking this operation.
2. Guard against calls made during startup: await the initialization promise or check the initialized flag and fail fast with a clear setup hint.

When it happens

Trigger: Thrown at v3/plugins/healthcare-clinical/src/bridges/gnn-bridge.ts:387 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of ruvnet/ruflo@fa13ee4ad6 (2026-08-18). Data as JSON: /api/errors/4e21bcd611b21d2e. Report an issue: GitHub.