Troubleshooting
This page is symptom-first.E_AUTH_REQUIRED
You tried a networked command without an effective token.
Typical fix:
E_AUTH_INVALID
The token was empty, malformed, or rejected by GitHub.
Checks:
- confirm the PAT is not empty
- confirm you pasted the correct token
- confirm you are targeting the right host
- re-run
auth login
E_QUERY_REQUIRED
You ran native search without a query:
- adding a query
- or switching to explicit discover mode with structured filters
E_FLAG_REQUIRES_MODE
You used a discover-only flag without --mode discover.
Example:
E_FLAG_CONFLICT
Two inputs overlap semantically.
Common examples:
- raw qualifier plus structured flag
- malformed
owner/repo - mixed date-window styles
E_HOST_INVALID
Your --host value is empty or malformed.
Good examples:
Missing Secure Storage
If keyring storage is unavailable, gitquarry will not silently drop to an insecure file. If you explicitly want the fallback path:Rate Limiting Or Slow Discovery
Gitquarry intentionally defaults--concurrency to 1 to avoid secondary rate limits.
If GitHub returns retry guidance, gitquarry backs off and retries up to a small bounded limit.
If you need the most predictable behavior: