LGUG2Z/komorebi · error
could not find file: {}
Error message
could not find file: {} What it means
Returned when komorebic is asked to read a file path that does not exist on disk (the formatting string receives the offending path). It is a straightforward existence check on user-supplied file input (e.g. a config file passed to a subcommand); the operation cannot proceed without the file.
Source
Thrown at komorebic/src/main.rs:2418
stdout if !stdout.contains("scoop") => None,
stdout => {
buf = PathBuf::from(stdout);
buf.pop(); // %USERPROFILE%\scoop\shims
buf.pop(); // %USERPROFILE%\scoop
buf.push("apps\\komorebi\\current\\komorebi.exe"); //%USERPROFILE%\scoop\komorebi\current\komorebi.exe
Some(buf.to_str().ok_or_eyre(
"cannot create a string from the scoop komorebi path",
)?)
}
}
} else {
None
};
let mut flags = vec![];
if let Some(config) = &args.config {
if !config.is_file() {
bail!("could not find file: {}", config.display());
}
let config = dunce::simplified(config);
flags.push(format!("'--config=\"{}\"'", config.display()));
}
if args.ffm {
flags.push("'--ffm'".to_string());
}
if args.await_configuration {
flags.push("'--await-configuration'".to_string());
}
if let Some(port) = args.tcp_port {
flags.push(format!("'--tcp-port={port}'"));
}
View on GitHub (pinned to e0709f02bf)
Solutions
- Verify the path in the message is spelled correctly and use an absolute path if needed
- Create the missing file or point the command at an existing one
- Check permissions/working directory if the file is expected to exist
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at komorebic/src/main.rs:2418 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of LGUG2Z/komorebi@e0709f02bf (2026-09-06).
Data as JSON: /api/errors/391e7c2a63a50f9c.
Report an issue: GitHub.