error[E0425]: cannot find function set_boxed_logger in crate log when building with Bazel/cargo-raze

[yesudeep]

Bug Report

Version

❯ cargo tree | grep tracing
│   ├── tracing v0.1.17
│   │   ├── tracing-attributes v0.1.9
│   │   └── tracing-core v0.1.11
│   ├── tracing-futures v0.2.4
│   │   └── tracing v0.1.17 (*)
│   └── tracing-subscriber v0.2.8
│       ├── tracing-core v0.1.11 (*)
│       ├── tracing-log v0.1.1
│       │   └── tracing-core v0.1.11 (*)
│       └── tracing-serde v0.1.1
│           └── tracing-core v0.1.11 (*)

I see that tracing-log has a dependency on the log package as well:

❯ cargo tree | grep log
│   │   │   ├── log v0.4.11
│       ├── tracing-log v0.1.1
│       │   ├── log v0.4.11 (*)

Platform

Darwin hostname 19.6.0 Darwin Kernel Version 19.6.0: Sun Jul  5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64 x86_64

Description

I'm trying out an example from the tokio documentation that uses mini-redis:

use mini_redis::{client, Result};

#[tokio::main]
pub async fn main() -> Result<()> {
    let mut client = client::connect("127.0.0.1:6379").await?;
    client.set("hello", "world".into()).await?;
    let result = client.get("hello").await?;
    println!("got value from the server; result={:?}", result);
    Ok(())
}

I get the following error:

❯ bazel run //codelab/rs/scratch:scratch
INFO: Analyzed target //codelab/rs/scratch:scratch (100 packages loaded, 2130 targets configured).
INFO: Found 1 target...
INFO: From Compiling Rust lib tracing_log v0.1.1 (5 files):
error[E0425]: cannot find function `set_boxed_logger` in crate `log`
   --> external/raze__tracing_log__0_1_1/src/log_tracer.rs:247:14
    |
247 |         log::set_boxed_logger(logger)?;
    |              ^^^^^^^^^^^^^^^^ not found in `log`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0425`.
ERROR: /Volumes/ether/bazel/f88229076ec69f23676bcfea768ed1a5/external/raze__tracing_log__0_1_1/BUILD.bazel:28:13: output 'external/raze__tracing_log__0_1_1/libtracing_log-717297689.rlib' was not created
ERROR: /Volumes/ether/bazel/f88229076ec69f23676bcfea768ed1a5/external/raze__tracing_log__0_1_1/BUILD.bazel:28:13: not all outputs were created or valid
Target //codelab/rs/scratch:scratch failed to build
INFO: Elapsed time: 5.278s, Critical Path: 0.77s
INFO: 4 processes: 4 darwin-sandbox.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully

I was expecting the example to compile successfully.

Thank you! :)

[hawkw]

Can you reproduce this outside of Bazel, with just Cargo? It would be nice to know whether this is a Bazel-specific issue, or if it effects all builds. Thanks!

[yesudeep]

I wasn't able to reproduce this with a plain Cargo-based directory.
You are correct. This appears to be Bazel/cargo-raze related.
I'll try to dig deeper and add more information here as I find.

[hawkw]

Thanks for checking!

I think this is likely related to feature flags in some way --- the set_boxed_logger function in log requires log's "std" feature to be enabled. tracing-subscriber enables "log/std" through its tracing-log dependency, which exposes its own feature flag to enable the log crate's feature:

tracing/tracing-subscriber/Cargo.toml

Line 43 in 0de7d51

tracing-log = { path = "../tracing-log", version = "0.1", optional = true, default-features = false, features = ["log-tracer", "std"] }

My guess is that either cargo-raze or Bazel's Rust rules are not able to handle this chain of features correctly?

[austintheriot]

If you find this by googling the error message like I did:

This issue was caused for me by Windows 10 Malwarebytes antivirus blocking a build script from running during compilation. Every time I ran a build, it would quarantine the file that was wanting to run a build for one of the dependencies. I had to add the crate directory to the allow list in order for the build to finish successfully. Not sure which script in particular it was, since I already added it to the allow list--sorry for lack of details there.

[aherrmann]

I bumped into a similar issue as described by @austintheriot above and to my understanding it is caused when log's build script is not run and cannot set the atomic_cas config, which is required next to the std feature to expose the symbol.

[psalaberria002]

@aherrmann did you figure out a solution? I am getting the same error.

error[E0425]: cannot find function `set_boxed_logger` in crate `log`
   --> external/crate_index__tracing-log-0.1.3/src/log_tracer.rs:292:14
    |
292 |         log::set_boxed_logger(logger)?;
    |              ^^^^^^^^^^^^^^^^ not found in `log`

error: aborting due to previous error

[aherrmann]

@psalaberria002 Yes, the solution for my use case was to make sure that the build.rs script runs and sets the atomic_cas configuration option.