ruvnet/ruflo · error · QESecurityError

Failed to create audit entry

Error message

Failed to create audit entry

What it means

Audit entry creation failed — typically the HS256 signing via security.tokenGenerator.sign threw (key/config problem) or building the entry itself failed, so no tamper-evident signed record is produced.

Source

Thrown at v3/plugins/agentic-qe/src/bridges/QESecurityBridge.ts:312

      };

      // Sign the entry with V3 token generator
      const signature = this.security.tokenGenerator.sign(
        JSON.stringify(entry),
        { algorithm: 'HS256' }
      );

      const signedEntry: SignedAuditEntry = {
        ...entry,
        signature,
        verifiable: true,
      };

      this.logger.debug(`Audit entry created: ${signedEntry.id}`);
      return signedEntry;
    } catch (error) {
      this.logger.error('Failed to create audit entry', error);
      throw new QESecurityError('Failed to create audit entry', error as Error);
    }
  }

  /**
   * Detect PII in content
   */
  async detectPII(content: string): Promise<PIIDetection[]> {
    const detections: PIIDetection[] = [];

    this.logger.debug('Scanning content for PII...');

    try {
      // Try to use V3's PII patterns first
      let patterns: Record<string, RegExp>;
      try {
        patterns = this.security.inputValidator.getPIIPatterns();
      } catch {
        // Fallback to built-in patterns

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Verify the audit sink (database/file) is writable and reachable; retry after fixing the underlying storage error.

When it happens

Trigger: Thrown at v3/plugins/agentic-qe/src/bridges/QESecurityBridge.ts:312 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/190ac331aa6e6236. Report an issue: GitHub.