ruvnet/ruflo · error
ExoticBridge not initialized
Error message
ExoticBridge not initialized
What it means
solveQubo() was called while this._module is null — i.e. initialize() has not completed (or dispose() ran). It is a lifecycle sentinel guard: the WASM/annealing module handle is missing, so the problem cannot be dispatched to any solver. Problem contents are not yet validated at this point.
Source
Thrown at v3/plugins/quantum-optimizer/src/bridges/exotic-bridge.ts:139
}
/**
* Dispose of resources
*/
async dispose(): Promise<void> {
this._module = null;
this._status = 'unloaded';
}
/**
* Solve a QUBO problem using simulated quantum annealing
*/
async solveQubo(
problem: QUBOProblem,
config: Partial<AnnealingConfig> = {}
): Promise<AnnealingResult> {
if (!this._module) {
throw new Error('ExoticBridge not initialized');
}
const mergedConfig = { ...DEFAULT_ANNEALING_CONFIG, ...config };
const startTime = performance.now();
// Validate problem
this.validateQuboProblem(problem);
// Run annealing
const samples: QUBOSolution[] = [];
const energyHistogram = new Map<number, number>();
for (let read = 0; read < mergedConfig.numReads; read++) {
const solution = this.simulatedAnnealing(problem, mergedConfig);
samples.push(solution);
const energyKey = Math.round(solution.energy * 1000) / 1000;
energyHistogram.set(energyKey, (energyHistogram.get(energyKey) ?? 0) + 1);View 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: validation
When it happens
Trigger: Thrown at v3/plugins/quantum-optimizer/src/bridges/exotic-bridge.ts:139 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/137044ae9371285d.
Report an issue: GitHub.