log level for os error is set to INFO level

[argnmp]

Problem

"cargo run" command in my environment has always tried to update crates.io index. ("Updating crates.io index")

I couldn't find out the reason why this happens until I debug cargo log using log level "debug"

2024-02-17T06:58:19.029438Z  INFO cargo::sources::registry::index: failed to write cache: Permission denied (os error 13)

The problem was that cargo did not have permission to write cache. The log level for "os error" was set to INFO, so I couldn't figure it out because default log level for CARGO_LOG is warn.

Steps

No response

Possible Solution(s)

It would be better to change log level for (os error) to "warn" or "error".

Notes

No response

Version

cargo 1.73.0 (9c4383fb5 2023-08-26)
release: 1.73.0
commit-hash: 9c4383fb55986096b414d98125421ab87b5fd642
commit-date: 2023-08-26
host: aarch64-apple-darwin
libgit2: 1.6.4 (sys:0.17.2 vendored)
libcurl: 8.4.0 (sys:0.4.65+curl-8.2.1 system ssl:(SecureTransport) LibreSSL/3.3.6)
ssl: OpenSSL 1.1.1u  30 May 2023
os: Mac OS 14.2.1 [64-bit]

[epage]

CARGO_LOG / logging is generally focused more on development related information. We generally control user facing information with --verbose / --quiet flags.

So if we exposed this, it would likely be a note: message that we report to the user. I suspect this was silenced to avoid annoying the user intentionally in this situation by printing a note on every command invocation. The downside being that you have to dig into the logs to figure out what is going on. If its not already, we could tie this note: to --verbose or --verbose --verbose so users don't have to go to logs to figure out what is going on.

[ehuss]

Note this is almost identical to #13712.

[ehuss]

This message has been changed to be a warning via #15014, so closing as resolved via that.