feat: executable command

[FroyaTheHen]

No description provided.

[maciektr]

This is not atomic, as we first ask OS whether the file exists or not and only then attempt creating it. It's prone to a race condition, as another process might have been scheduled by the OS between call to file metadata (exists) and call to create it.
Instead, please do:

        let file = OpenOptions::new().create_new(true).open(path.as_std_path());
        return match file {
            Err(e) => {
                if e.kind() == std::io::ErrorKind::AlreadyExists {
                    continue;
                }
                Err(e.into())
            }
            Ok(_) => Ok(filepath),
        };

.create_new(true) ensures new file will be created, or else AlreadyExists thrown.
If the file has not been created because of some error, other than already exist (e.g. running out of disk space) we can show the error to the user.

Similar approach can be used for directories:

        let dir = fs::create_dir(&filepath);
        return match dir {
            Err(e) => {
                if e.kind() == std::io::ErrorKind::AlreadyExists {
                    continue;
                }
                Err(e.into())
            }
            Ok(_) => Ok(filepath),

[FroyaTheHen]

cargo clippy warns agains using canonicalize(), should i use fsx::canonicalize_utf8 does it apply in this case? please advise

[maciektr]

Yes, you should. fsx is basically our wrapper over path manipulation functions that handles some edge-cases that we have run into in the past. The clippy lint you see has been added by us here

scarb/clippy.toml

Line 1 in f1e8abb

disallowed-methods = [

[maciektr]

Replaced with #1885