Some '${fieldName}' remotes are not non-empty strings; the i

Error message

Some '${fieldName}' remotes are not non-empty strings; the ids are kept without a clone source

What it means

Error "Some '${fieldName}' remotes are not non-empty strings; the ids are kept without a clone source" thrown in Fission-AI/OpenSpec.

Source

Thrown at src/core/project-config.ts:239

    if (!declaration) {
      droppedEntries = true;
      continue;
    }

    const existing = byId.get(declaration.id);
    if (!existing) {
      byId.set(declaration.id, declaration);
    } else if (existing.remote === undefined && declaration.remote !== undefined) {
      existing.remote = declaration.remote;
    }
  }

  if (droppedEntries) {
    console.warn(`Some '${fieldName}' entries are invalid, ignoring them`);
  }
  if (droppedRemotes) {
    console.warn(
      `Some '${fieldName}' remotes are not non-empty strings; the ids are kept without a clone source`
    );
  }
  return byId.size > 0 ? [...byId.values()] : undefined;
}

export const MAX_CONTEXT_SIZE = 50 * 1024; // 50KB hard limit, shared with the references index

/**
 * Read and parse openspec/config.yaml from project root.
 * Uses resilient parsing - validates each field independently using Zod safeParse.
 * Returns null if file doesn't exist.
 * Returns partial config if some fields are invalid (with warnings).
 *
 * Performance note (Jan 2025):
 * Benchmarks showed direct file reads are fast enough without caching:
 * - Typical config (1KB): ~0.5ms per read
 * - Large config (50KB): ~1.6ms per read

View on GitHub (pinned to 6926ccb18a)

When it happens

Trigger: Thrown at src/core/project-config.ts:239 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of Fission-AI/OpenSpec@6926ccb18a (2026-08-25). Data as JSON: /api/errors/23dd6b8507edd6a4. Report an issue: GitHub.