ruvnet/ruflo · error

Non-dry-run chaos injection requested - proceeding with simu

Error message

Non-dry-run chaos injection requested - proceeding with simulation

What it means

Safety notice in the chaos-inject MCP tool handler: the request specified dryRun=false (real chaos injection). Because explicit confirmation cannot be obtained through the MCP interface, the handler downgrades the request to simulation and proceeds, warning the caller.

Source

Thrown at v3/plugins/agentic-qe/src/tools/chaos-resilience/chaos-inject.ts:159

/**
 * MCP Tool Handler for chaos-inject
 */
export async function handler(
  input: ChaosInjectInput,
  context: ToolContext
): Promise<{ content: Array<{ type: 'text'; text: string }> }> {
  const startTime = Date.now();
  const experimentId = `chaos-${Date.now()}-${Math.random().toString(36).substring(7)}`;

  try {
    // Validate input
    const validatedInput = ChaosInjectInputSchema.parse(input);

    // SAFETY: Check for dry run mode
    if (!validatedInput.dryRun) {
      // In a real implementation, would require explicit confirmation
      // For MCP tool, we default to dry run for safety
      console.warn('Non-dry-run chaos injection requested - proceeding with simulation');
    }

    // Generate experiment timeline
    const timeline: TimelineEvent[] = [];
    const experimentStart = new Date().toISOString();

    timeline.push({
      timestamp: experimentStart,
      event: 'Experiment initialized',
      type: 'info',
      details: `Chaos experiment ${experimentId} created for ${validatedInput.target}`,
    });

    // Capture baseline metrics
    const baseline = captureMetricSnapshot('baseline');
    timeline.push({
      timestamp: new Date().toISOString(),
      event: 'Baseline captured',

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Run with dry-run enabled first to preview the chaos injection effects before applying them.
2. Confirm the target environment is non-production before allowing non-dry-run injection.
3. Require an explicit confirmation flag for non-dry-run chaos injection.

When it happens

Trigger: Chaos injection invoked without dryRun=true; tool proceeds to simulate the fault (latency, error, or resource failure) against the target service for resilience testing.

Common situations: See trigger scenarios.

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