BerriAI/litellm · error · Exception

Error getting file metadata for '{file_path}': {e}

Error message

Error getting file metadata for '{file_path}': {e}

What it means

Non-HTTP branch of get_file_metadata's error handler: the raised exception has no .response attribute, meaning the request never got a response or failed locally — DNS/connectivity errors, TLS failures, or an exception while reading response headers. The original error is preserved only as a string inside the message.

Source

Thrown at litellm/integrations/bitbucket/bitbucket_client.py:245

            headers: Final = self.headers.copy()
            headers["Range"] = "bytes=0-0"  # Request only first byte to get headers

            response: Final = self.http_handler.get(url, headers=headers)
            response.raise_for_status()

            return {
                "content_type": response.headers.get("content-type"),
                "content_length": response.headers.get("content-length"),
                "last_modified": response.headers.get("last-modified"),
            }
        except Exception as e:
            # Check if it's an HTTP error
            if hasattr(e, "response") and hasattr(e.response, "status_code"):
                if e.response.status_code == 404:
                    return None
                raise Exception(f"Failed to get file metadata for '{file_path}': {e}")
            else:
                raise Exception(f"Error getting file metadata for '{file_path}': {e}")

    def close(self):
        """Close the HTTP handler to free resources."""
        if hasattr(self, "http_handler"):
            self.http_handler.close()

View on GitHub (pinned to 6c2dcb801b)

Solutions

1. Verify egress: curl -I https://api.bitbucket.org/2.0/user from the same container
2. Configure HTTPS_PROXY if a corporate proxy is required
3. Wrap calls in retry-with-backoff for transient connectivity drops
4. Treat metadata as optional — catch and return None so prompt loading can proceed on cached content

Example fix

# before
meta = client.get_file_metadata(path)

# after (metadata is best-effort)
try:
    meta = client.get_file_metadata(path)
except Exception as e:
    if not hasattr(getattr(e, "__context__", None), "response"):
        logger.warning("BitBucket unreachable, skipping metadata refresh for %s", path)
        meta = None
    else:
        raise

import socket

def can_reach_bitbucket() -> bool:
    try:
        socket.create_connection(("api.bitbucket.org", 443), timeout=3).close()
        return True
    except OSError:
        return False

try:
    meta = client.get_file_metadata(path)
except Exception as e:
    ctx = getattr(e, "__context__", None)
    if ctx is not None and hasattr(ctx, "response"):
        raise  # HTTP error, different bucket
    meta = None  # network blip — proceed without metadata

When it happens

Trigger: Calling get_file_metadata() in an environment that cannot reach api.bitbucket.org (connection refused, DNS failure), a corporate proxy terminating the connection, or a client certificate/TLS handshake failure.

Common situations: LiteLLM proxy deployed in a locked-down Kubernetes cluster without egress rules for api.bitbucket.org; missing HTTPS_PROXY in corporate networks; transient network interruptions during scheduled metadata sync.

Related errors

• Error listing files in '{directory_path}': {e}
• Error fetching file '{file_path}': {e}
• Failed to get file metadata for '{file_path}': {e}
• Mavvrik FOCUS destination: GCS session init missing Location
• Failed to fetch provider mapping: {e}

AI-assisted analysis of BerriAI/litellm@6c2dcb801b (2026-08-15). Data as JSON: /api/errors/aa1bde7648cc48e7. Report an issue: GitHub.