ruvnet/ruflo · error

[WASM Loader] detect_cycles failed, using fallback:

Error message

[WASM Loader] detect_cycles failed, using fallback:

What it means

Log warning in detectCycles: the WASM detect_cycles invocation failed; cycle detection reruns through the JavaScript fallback implementation.

Source

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

export async function detectCycles(
  nodes: string[],
  edges: GraphEdge[]
): Promise<CycleDetectionResult> {
  const startTime = performance.now();

  const wasmModule = await loadGnnWasm();

  if (wasmModule) {
    try {
      const resultJson = wasmModule.detect_cycles(
        JSON.stringify(nodes),
        JSON.stringify(edges)
      );
      const result = JSON.parse(resultJson) as CycleDetectionResult;
      recordTiming('detectCycles', startTime, true);
      return result;
    } catch (error) {
      console.warn('[WASM Loader] detect_cycles failed, using fallback:', error);
    }
  }

  // JavaScript fallback
  const result = detectCyclesFallback(nodes, edges);
  recordTiming('detectCycles', startTime, false);
  return result;
}

/**
 * Calculate the critical path through a weighted dependency graph.
 * Uses WASM if available (150x faster), falls back to JavaScript.
 *
 * @param nodes - Array of node identifiers
 * @param edges - Array of edges (from -> to dependencies)
 * @param weights - Array of node weights (durations)
 * @returns Critical path result with path, duration, and slack times
 *

View on GitHub (pinned to fa13ee4ad6)

Solutions

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

When it happens

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