ruvnet/ruflo · error · Error
WASM module not available
Error message
WASM module not available
What it means
analyzeWithWasm() found this.wasmModule null — dependency analysis was requested through the WASM path but the WASM module never loaded. The method is only called when useWasm is configured, so this indicates a loader failure the caller should fall back from.
Source
Thrown at v3/plugins/gastown-bridge/src/convoy/observer.ts:842
status: bead.status,
priority: bead.priority,
blocked_by: bead.blockedBy ?? [],
blocks: bead.blocks ?? [],
duration: undefined,
}));
}
/**
* Analyze dependencies with WASM
*/
private analyzeWithWasm(beads: Bead[]): {
hasCycles: boolean;
cycleIssues: string[];
readyIssues: ReadyIssueInfo[];
blockedIssues: BlockerInfo[];
} {
if (!this.wasmModule) {
throw new Error('WASM module not available');
}
const wasmNodes = this.beadsToWasmNodes(beads);
const beadsJson = JSON.stringify(wasmNodes);
// Check for cycles
const hasCycles = this.wasmModule.has_cycle(beadsJson);
let cycleIssues: string[] = [];
if (hasCycles) {
const cycleJson = this.wasmModule.find_cycle_nodes(beadsJson);
cycleIssues = JSON.parse(cycleJson);
}
// Get ready beads
const readyJson = this.wasmModule.get_ready_beads(beadsJson);
const readyIds: string[] = JSON.parse(readyJson);
// Get execution levelsView on GitHub (pinned to fa13ee4ad6)
Solutions
- Ensure the module/bridge/plugin initialize() method has been called and awaited before invoking this operation.
- Guard against calls made during startup: await the initialization promise or check the initialized flag and fail fast with a clear setup hint.
Defensive patterns
Strategy: type-guard
When it happens
Trigger: Thrown at v3/plugins/gastown-bridge/src/convoy/observer.ts:842 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/7b11449f15394681.
Report an issue: GitHub.