What causes "{}" in tonhowtf/omniget?

Read the interpolated message to see the underlying failure (network vs. fs::write)

{}

Error message

{}

What it means

fetch_one downloads a single emote image and, after retrying, throws with the message of the last failure ('{}' interpolates the final error). It is reached only when every attempt to produce a valid file failed, typically the raw last I/O or network error is surfaced verbatim.

Solutions

Read the interpolated message to see the underlying failure (network vs. fs::write)
Ensure the output directory exists and is writable before running
Retry — transient CDN/network failures often resolve
Verify the emote still exists on its provider (URL may be stale)

Example fix

// before
std::fs::create_dir_all(out_dir); // forgotten entirely
let set = fetch_all(...).await?;
// after
std::fs::create_dir_all(out_dir)?;
let set = fetch_all(...).await?;

Defensive patterns

Strategy: try-catch

Validate before calling

// Ensure the output directory exists and is writable before fetching.
std::fs::create_dir_all(out_dir)?;
let probe = out_dir.join(".write-test");
std::fs::write(&probe, b"")?;
std::fs::remove_file(&probe)?;

Try / catch

match fetch_one(&emote, &path).await {
    Err(e) if e.to_string().contains("arquivo vazio") || e.is::<std::io::Error>() => {
        tracing::warn!("emote {} failed, skipping: {}", emote.name, e);
    }
    other => other?,
}

Prevention

Create and verify the output directory before downloading
Retry once on transient network failures before giving up
Check provider URLs still resolve (stale CDN links 404)
Run with write permission to the target directory

When it happens

Trigger: run() calling fetch_one for an emote whose download repeatedly failed (network error, 404 from a stale CDN URL) or whose std::fs::write to the output path failed (permission denied, no such directory) — the last attempt's error text becomes the message.

Common situations: Provider API returning dead/renamed emote URLs; output directory not existing or read-only filesystem; antivirus or permissions blocking the write; transient network drops exhausting retries.

Understand the failure class

Background: 'Something went wrong' / 'Request failed (500)' / 'HTTP error! status: 404' — what failed HTTP requests actually mean and how to find the real cause — this error's family across 28 libraries.

Related errors

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

Appendix: source

Thrown at src-tauri/omniget-core/src/core/tools/twitch/emotes.rs:839

                continue;
            }
        };
        let status = resp.status();
        if status.as_u16() == 429 || status.is_server_error() {
            last = format!("HTTP {}", status);
            continue;
        }
        if !status.is_success() {
            anyhow::bail!("HTTP {}", status);
        }
        let bytes = resp.bytes().await?;
        if bytes.is_empty() {
            anyhow::bail!("arquivo vazio");
        }
        std::fs::write(path, &bytes)?;
        return Ok(());
    }
    Err(anyhow!("{}", last))
}

#[cfg(test)]
mod tests {
    use super::*;

    #[test]
    fn le_emotes_e_badges_da_twitch() {
        let user = json!({
            "subscriptionProducts": [
                { "emotes": [
                    { "id": "emotesv2_abc", "token": "xqcSlam", "assetType": "ANIMATED" },
                    { "id": "305535174", "token": "xqcOmega", "assetType": "STATIC" }
                ]}
            ],
            "broadcastBadges": [
                { "setID": "subscriber", "version": "0", "title": "Subscriber",
                  "imageURL": "https://static-cdn.jtvnw.net/badges/v1/abc/3" }

View on GitHub (pinned to 8600b91f42)