rules_rust "Downloaded xxx" and "Compiling xxx" log spam

I'm getting over 400 lines of "Downloaded xxx" and "Compiling xxx" before "Finished release profile [optimized] target(s) in 51.94s". Is there a way to reduce that log spam?

I know Cargo has a --quiet option but it's not immediately obvious to me where in rules_rust that would have to be added. Any pointers?

Aug 30 '24 08:08 lalten

Where do you see this? Can you post some logs?

Aug 31 '24 04:08 UebelAndre

Here is a bazel coverage invocation, but I've also seen it happen on bazel mod deps --lockfile_mode=update and other calls. It's likely related to having a fresh cache on a new CI runner.

Sep 03 '24 12:09 lalten

What version of rules_rust are you using?

Sep 03 '24 13:09 UebelAndre

Currently on 0.46.0 (with some minor patches like adding requires-network execution_requirements for a custom rustc with QNX support and adding custom target triples)

Sep 04 '24 08:09 lalten

I just observed this in https://github.com/lalten/appimage-runtime-rs/actions/runs/10760111232/job/29837618758. rules_rust is at current main without any patches in that branch.

Sep 08 '24 13:09 lalten

Is bzlmod not using the release artifacts? On main there are no pre-built cargo-bazel binaries available so in order to generate 3rdparty dependencies with crate_universe the binary needs to be bootstrapped. If you're using releases or build your own cargo_bazel attribute (though I'm not sure if this is exposed to bzlmod). I'd be happy to review pull requests that made configuring this clearer and easier 😄

Sep 12 '24 16:09 UebelAndre

It looks like the issue was indeed that the bazel_dep() pointed at specific commits rather than releases! Maybe it would make sense to print a message informing the user about what's happening?

Nov 05 '24 19:11 lalten