Surface Wrong-Cluster Clone Errors Clearly

Claude Code·Opus 4.8[1m]·toothbrush·3mo ago·39min·2 Checkpoints·5 file changes·+107/-11·24.5K tokens

in git-remote-entire, let's special case this error message and surface it nicely to the user:

09:55:27 $ git clone entire://aws-us-east-2.entire.io/et/paul/dogbark "$(mktemp -d)" Cloning into '/var/folders/vw/c9lnz3m55v124_2h0hv7p4lh0000gn/T/tmp.jwCHMfmsWg'... fatal: stateless-connect v2 info/refs: fetching info/refs from entry domain: repo-scoped token exchange: oauth token exchange: HTTP 400: {"error":"invalid_target","error_description":"audience host "aws-us-east-2.entire.io" does not host this repo; it lives on "aws-eu-central-1.entire.io" — re-target the request there"}

new branch and open a PR

3mo ago·5m

Done. PR opened: https://github.com/entireio/cli/pull/1575

What changed:

  • httputil.OAuthError now captures error_description (RFC 6749).
  • git-remote-entire digs the buried OAuthError out via errors.As; for invalid_target whose description names the hosting cluster, it prints an actionable message + corrected git clone entire://... URL instead of the raw HTTP 400 chain.

Before: fatal: stateless-connect v2 info/refs: ... HTTP 400: {"error":"invalid_target",...} After: fatal: this repository is not hosted on aws-us-east-2.entire.io; it lives on aws-eu-central-1.entire.io. + the corrected clone command.

Notes:

  • Only the wrong-cluster case (description matches lives on "<host>") is special-cased; other invalid_target variants (e.g. suspended mirror) fall back verbatim.
  • Pushed to origin, but PR had to be created with --repo entireio/cli since gh doesn't recognize the entire:// remotes.
97aa0c9feat(git-remote-entire): surface wrong-cluster clone errors clearly When a repo lives on a different cluster than the one in the entire:// URL, the data plane rejects the token exchange with an RFC 8693 invalid_target carrying an error_description naming the correct host. Previously this surfaced as a raw, multiply-wrapped HTTP 400 JSON blob. Now git-remote-entire detects this case and prints an actionable message naming the correct host and the corrected `git clone entire://...` URL. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Entire-Checkpoint: 7cf3c440ed71+96/-6

let's fix this. https://github.com/entireio/cli/pull/1575/files#discussion_r3495473008

3mo ago·1m

Both review comments addressed. Committed (not pushed, per your workflow).

  • r3495473008 (linked): TestPostOAuthToken_ErrorCode now asserts OAuthError.Description for both JSON and non-JSON bodies, so the wrong-cluster UX can't silently regress.
  • The other Copilot comment: corrected URL now copies the user's parsed URL and swaps only the host, preserving RawPath/query escaping instead of dropping them.

Tests + lint green. Push when ready.

614570etest(httputil): assert error_description is captured; preserve URL escaping Addresses PR review: - Pin OAuthError.Description extraction so the git-remote-entire wrong-cluster UX can't silently regress. - Rebuild the corrected entire:// URL from the user's parsed URL with only the host swapped, preserving RawPath/query escaping. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Entire-Checkpoint: ef974a99a5c2+11/-5