tonhowtf/omniget · error · anyhow::Error

Failed to move into place

Error message

Failed to move {} into place: {}

What it means

Thrown by replace_managed_binary when the target binary does not exist yet and the initial std::fs::rename(temp, target) fails (moving the freshly downloaded temp file into its final location). The message includes the target path and the io::Error.

Solutions

1. Create the target's parent directory before calling replace_managed_binary (fs::create_dir_all).
2. Ensure the process has write permission on the target directory.
3. Place the temp file on the same filesystem/volume as the target to avoid cross-device rename errors.
4. Read the wrapped io::Error for the exact errno (e.g. EXDEV, EACCES) and address accordingly.

Example fix

// before
replace_managed_binary(&temp, &target)?;
// after
if let Some(dir) = target.parent() { std::fs::create_dir_all(dir)?; }
replace_managed_binary(&temp, &target)?;

// Rust: ensure destination dir exists and is writable before replacing
fn target_dir_ready(target: &std::path::Path) -> std::io::Result<()> {
    let dir = target.parent().ok_or_else(|| std::io::Error::new(std::io::ErrorKind::InvalidInput, "no parent"))?;
    std::fs::create_dir_all(dir)?;
    let probe = dir.join(".write_probe");
    std::fs::write(&probe, b"")?;
    std::fs::remove_file(&probe)
}

match replace_managed_binary(&temp, &target) {
    Ok(()) => {},
    Err(e) => { log::error!("install move failed: {e:#}"); return Err(e); }
}

When it happens

Trigger: download_ffmpeg calls replace_managed_binary with a target path whose parent directory is missing, is read-only, or spans a different filesystem from temp (rename across devices returns EXDEV).

Common situations: Fresh install where the managed-binaries directory was never created; permission problems under Program Files or system-wide install paths; temp dir on another mount/partition.

Understand the failure class

Background: "failed to write file", "Could not save figure", "Error saving remote file" — file write failed: causes and fixes across languages and libraries — this error's family across 38 libraries.

Related errors

• nao foi possivel mover a instalacao para o lugar
• nao leu
• pasta de origem não encontrada
• Failed to replace
• Could not determine data directory

AI-assisted analysis of tonhowtf/omniget@8600b91f42 (2026-09-12). Data as JSON: /api/errors/733d75913088ddf8. Report an issue: GitHub.

Appendix: source

Thrown at src-tauri/omniget-core/src/core/dependencies.rs:330

pub async fn check_version(tool: &str) -> Option<String> {
    let _timer_start = std::time::Instant::now();
    let path = find_tool(tool).await?;
    let result = check_version_at_path(&path, tool).await;
    tracing::debug!(
        "[perf] check_version({}) took {:?}",
        tool,
        _timer_start.elapsed()
    );
    result
}

pub fn replace_managed_binary(
    temp: &std::path::Path,
    target: &std::path::Path,
) -> anyhow::Result<()> {
    if !target.exists() {
        std::fs::rename(temp, target)
            .map_err(|e| anyhow!("Failed to move {} into place: {}", target.display(), e))?;
        return Ok(());
    }

    if cfg!(windows) {
        let file_name = target
            .file_name()
            .and_then(|n| n.to_str())
            .unwrap_or("binary")
            .to_string();
        let old = target.with_file_name(format!("{}.old", file_name));
        let _ = std::fs::remove_file(&old);
        if let Err(e) = std::fs::rename(target, &old) {
            let _ = std::fs::remove_file(temp);
            return Err(anyhow!(
                "{} is in use by another process ({}). Wait for active downloads to finish or cancel them, then try again.",
                file_name,
                e
            ));

View on GitHub (pinned to 8600b91f42)