ruvnet/ruflo · error

[Discovery] Fetch from ${gateway} failed:

Error message

[Discovery] Fetch from ${gateway} failed:

What it means

Log warning in fetchRegistry: fetching the registry JSON from one gateway failed (timeout, network, or invalid JSON); the loop proceeds to the next configured gateway.

Source

Thrown at v3/@claude-flow/cli/src/transfer/store/discovery.ts:262

    console.log(`[Discovery] Fetching: ${url}`);

    try {
      const response = await fetch(url, {
        signal: AbortSignal.timeout(30000),
      });

      if (response.ok) {
        const text = await response.text();
        try {
          const registry = JSON.parse(text) as PatternRegistry;
          console.log(`[Discovery] Fetched registry with ${registry.patterns?.length || 0} patterns`);
          return registry;
        } catch {
          console.error(`[Discovery] Invalid registry JSON`);
        }
      }
    } catch (error) {
      console.warn(`[Discovery] Fetch from ${gateway} failed:`, error);
    }

    // Try alternative gateways
    const alternativeGateways = [
      'https://ipfs.io',
      'https://dweb.link',
      'https://cloudflare-ipfs.com',
      'https://gateway.pinata.cloud',
    ];

    for (const altGateway of alternativeGateways) {
      if (altGateway === gateway) continue;
      try {
        const altUrl = `${altGateway}/ipfs/${cid}`;
        console.log(`[Discovery] Trying alternative: ${altUrl}`);

        const response = await fetch(altUrl, {
          signal: AbortSignal.timeout(15000),

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Check the gateway-specific error; the next gateway is tried automatically. If all fail, verify the CID and outbound network access.

When it happens

Trigger: Thrown at v3/@claude-flow/cli/src/transfer/store/discovery.ts:262 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/d89f66a9f4f8908a. Report an issue: GitHub.