zed-industries/zed · error
Git Clone failed
Error message
Git Clone failed
What it means
The remote git clone RPC (proto::GitClone) sent to the host failed — the request itself returned an error rather than completing. The host-side clone likely failed (bad URL, auth, disk) or the connection dropped mid-request.
Source
Thrown at crates/project/src/git_store.rs:3168
..
} => {
if upstream_client.is_via_collab() {
return Task::ready(Err(anyhow!(
"Git Clone isn't supported for project guests"
)));
}
let request = upstream_client.request(proto::GitClone {
project_id: *upstream_project_id,
abs_path: path.to_string_lossy().into_owned(),
remote_repo: repo,
});
cx.background_spawn(async move {
let result = request.await?;
match result.success {
true => Ok(()),
false => Err(anyhow!("Git Clone failed")),
}
})
}
}
}
pub fn git_config(&self, path: Arc<Path>, args: Vec<String>, cx: &App) -> Task<Result<String>> {
match &self.state {
GitStoreState::Local { fs, .. } => {
let fs = fs.clone();
cx.background_executor()
.spawn(async move { fs.git_config(&path, args).await })
}
GitStoreState::Remote {
upstream_client, ..
} => {
// Prevent running git config commands for collab.
if upstream_client.is_via_collab() {View on GitHub (pinned to f4178619ac)
Solutions
- Check the host's logs for the underlying clone failure
- Verify the repository URL and credentials, and available disk space on the host
- Retry after fixing the cause; transient connection drops can simply be retried
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at crates/project/src/git_store.rs:3168 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of zed-industries/zed@f4178619ac (2026-08-20).
Data as JSON: /api/errors/f465c1640a6a83cc.
Report an issue: GitHub.