ruvnet/ruflo · error

[WASM Loader] critical_path failed, using fallback:

Error message

[WASM Loader] critical_path failed, using fallback:

What it means

Log warning in criticalPath: the WASM critical_path computation threw (or its result JSON failed to parse); the JS fallback computes the critical path and slack values.

Source

Thrown at v3/plugins/gastown-bridge/src/wasm-loader.ts:1079

  if (wasmModule) {
    try {
      const resultJson = wasmModule.critical_path(
        JSON.stringify(nodes),
        JSON.stringify(edges),
        JSON.stringify(weights)
      );
      const parsed = JSON.parse(resultJson);
      // Convert slack array back to Map
      const result: CriticalPathResult = {
        path: parsed.path,
        totalDuration: parsed.totalDuration,
        slack: new Map(Object.entries(parsed.slack).map(([k, v]) => [k, v as number])),
      };
      recordTiming('criticalPath', startTime, true);
      return result;
    } catch (error) {
      console.warn('[WASM Loader] critical_path failed, using fallback:', error);
    }
  }

  // JavaScript fallback
  const result = criticalPathFallback(nodes, edges, weights);
  recordTiming('criticalPath', startTime, false);
  return result;
}

// ============================================================================
// Module Management
// ============================================================================

/**
 * Preload all WASM modules.
 * Call this during initialization for best performance.
 *
 * @returns Object indicating which modules were loaded

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Check the graph input and the WASM critical_path error; the JS fallback is used.

When it happens

Trigger: Thrown at v3/plugins/gastown-bridge/src/wasm-loader.ts:1079 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/4431a8d872f9122a. Report an issue: GitHub.