cros-codecs declares log = { version = "0", features = ["release_max_level_debug"] } in its Cargo.toml. Because Cargo features are additive and global, this forces the release_max_level_debug setting on all downstream users, and conflicts with any application that sets a different release_max_level_*, causing a compile error:
error: multiple release_max_level_* features set
The log crate docs recommend that only final binaries set these features, not libraries (like cros_codecs).
I suggest fixing this by removing features = ["release_max_level_debug"] from the log dependency and let consuming applications decide their own log level filtering, as per the log crate's recommendations.
cros-codecsdeclareslog = { version = "0", features = ["release_max_level_debug"] }in its Cargo.toml. Because Cargo features are additive and global, this forces therelease_max_level_debugsetting on all downstream users, and conflicts with any application that sets a differentrelease_max_level_*, causing a compile error:The
logcrate docs recommend that only final binaries set these features, not libraries (likecros_codecs).I suggest fixing this by removing
features = ["release_max_level_debug"]from the log dependency and let consuming applications decide their own log level filtering, as per thelogcrate's recommendations.