Weihang Lo

@Itxaka Just FYI, for v1.0.01-rc3 we haven't got a time to upgrade cOS-toolkit. Instead, we patched it manually https://github.com/harvester/harvester-installer/pull/266

Hey @sikula. If you don't have time working on this, would you mind me pushing this forward based on this PR?

M1 result here. (with commit 044871f) Click to expand ``` $ sysctl -a | grep brand_string machdep.cpu.brand_string: Apple M1 Pro $ cargo run --example simple Compiling ... Finished dev [unoptimized...

Now looks nicer. Sorry I didn't look into it more, and thanks for your quick fix, @Mark3K ! click to expand ``` $ cargo run --example simple Compiling sysinfo v0.25.1...

FWIW, the security concern might be mitigated a bit after got merged.

> What is the current recommendation to get the final output name? Another workaround with `jq`. Use at your own risk: ``` cargo build --message-format=json -q | jq -r 'select(.target.kind[0]...

We appreciate Alex efforts on Cargo and Alex has already retired from the Cargo Team.[^1] There was a previous attempt and concerns were listed . Feel free to pick it...

Thanks for the suggestion. AFAIK, Cargo doesn't have the convention mentioning a specific flag in the headline of help text, and some other tools display help text inline (e.g. fish)....

FWIW, `cargo-add` is one attempt to adopt the pattern: `-h` for a short briefer; `--help` for a longer one, and `help ` is a complete reference. This approach may also...

If it is related to git clone, perhaps set the config [`net.git-fetch-with-cli = true`](https://doc.rust-lang.org/cargo/reference/config.html#netgit-fetch-with-cli) to see whether libgit2 is the suspect.