lapce/lapce · error
can't find proxy directory
Error message
can't find proxy directory
What it means
Error "can't find proxy directory" thrown in lapce/lapce.
Source
Thrown at lapce-app/src/proxy/remote.rs:337
};
if !script_install.success() {
let cmd = match platform {
HostPlatform::Windows => remote
.command_builder()
.args(["dir", remote_proxy_file])
.status()?,
_ => remote
.command_builder()
.arg("test")
.arg("-e")
.arg(remote_proxy_file)
.status()?,
};
if !cmd.success() {
let proxy_filename = format!("lapce-proxy-{platform}-{architecture}");
let local_proxy_file = Directory::proxy_directory()
.ok_or_else(|| anyhow!("can't find proxy directory"))?
.join(&proxy_filename);
// remove possibly outdated proxy
if local_proxy_file.exists() {
// TODO: add proper proxy version detection and update proxy
// when needed
std::fs::remove_file(&local_proxy_file)?;
}
let proxy_version = match meta::RELEASE {
meta::ReleaseType::Stable => meta::VERSION,
_ => "nightly",
};
let url = format!(
"https://github.com/lapce/lapce/releases/download/{proxy_version}/{proxy_filename}.gz"
);
debug!("proxy download URI: {url}");
let mut resp = lapce_proxy::get_url(url, None).expect("request failed");
if resp.status().is_success() {
let mut out = std::fs::File::create(&local_proxy_file)View on GitHub (pinned to c9e4c33948)
When it happens
Trigger: Thrown at lapce-app/src/proxy/remote.rs:337 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of lapce/lapce@c9e4c33948 (2026-08-16).
Data as JSON: /api/errors/49d5148b14bf5bcd.
Report an issue: GitHub.