github/spec-kit · error · BundlerError
Failed to fetch catalog from {url}: {exc}
Error message
Failed to fetch catalog from {url}: {exc} What it means
Error "Failed to fetch catalog from {url}: {exc}" thrown in github/spec-kit.
Source
Thrown at src/specify_cli/bundler/services/adapters.py:203
try:
with open_url(
url,
timeout=HTTP_TIMEOUT_SECONDS,
redirect_validator=_validate_redirect,
) as response:
final_url = response.geturl()
_validate_remote_url(source_id, final_url)
raw = read_response_limited(
response,
max_bytes=MAX_JSON_CATALOG_BYTES,
error_type=BundlerError,
label=f"bundle catalog '{source_id}'",
).decode("utf-8")
except BundlerError:
raise
except Exception as exc: # noqa: BLE001
raise BundlerError(f"Failed to fetch catalog from {url}: {exc}") from exc
return loads_json(raw, origin=final_url)
class DefaultPrimitiveInstaller:
"""Dispatch component install/remove to existing primitive machinery.
This adapter is intentionally thin: it owns no install logic of its own,
delegating entirely to the per-primitive managers so the bundler honours
Principle I (no duplicated primitive logic).
*allow_network* mirrors the bundle command's ``--offline`` flag: when False,
component kinds that can only be sourced from a remote catalog refuse rather
than touching the network. Bundled presets/extensions still install offline.
"""
def __init__(self, *, allow_network: bool = True) -> None:
self._allow_network = allow_network
View on GitHub (pinned to bf88c9f9a8)
Solutions
- Check network connectivity and the catalog URL, verify credentials if the host requires auth, then retry the fetch.
When it happens
Trigger: Thrown at src/specify_cli/bundler/services/adapters.py:203 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of github/spec-kit@bf88c9f9a8 (2026-08-14).
Data as JSON: /api/errors/715aa1a02f1acdec.
Report an issue: GitHub.