Skip to main content

Error Reference

Gitquarry returns one clear error at a time.

Common Error Codes

E_AUTH_REQUIRED

No effective credential was available for the current host. Typical fix:
gitquarry auth login

E_AUTH_INVALID

The token was empty, rejected, or invalid for the attempted operation.

E_AUTH_STORAGE

Credential storage failed. Common causes:
  • local secure storage backend unavailable
  • insecure fallback not explicitly enabled
  • malformed insecure credential file

E_FLAG_PARSE

Clap-level flag parse failure, such as an invalid enum value.

E_FLAG_CONFLICT

Two flags or inputs conflict semantically. Examples:
  • mixed date-window styles
  • invalid blended weights
  • raw qualifier plus overlapping structured flag

E_FLAG_REQUIRES_MODE

A flag requires --mode discover. Typical examples:
  • non-native --rank
  • discovery-only --depth
  • advanced enrichment knobs

E_QUERY_REQUIRED

A plain native search was attempted without a query.

E_GITHUB_API

GitHub returned a non-success API response that gitquarry could not treat as a normal optional case.

E_HTTP

Transport, request, or decode failure.

E_CONFIG_PATH

Gitquarry could not determine the user config directory.

E_CONFIG_IO

Config or config-directory I/O failed.

E_CONFIG_PARSE

config.toml existed but could not be parsed.

E_HOST_INVALID

The --host value was empty or malformed.

E_NOT_FOUND

An optional GitHub resource was not found. This is often handled internally for README or latest-release fetches, but can still surface in some flows.

E_OUTPUT

Stdout, stderr, JSON, CSV, or help rendering failed.

E_STORAGE

Local credential-file read or write failed outside the secure-storage happy path.

Operational Notes

Gitquarry intentionally stops at the first clear error. It does not emit a batch of speculative fixes.