You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm setting up a Rust mono repo with > 35 crates. I am generating all dependencies with crate_universe, exactly as described in the documentation. While configuring Bazel for the first crate, I stumbled across the following error when running bazel build
defined by /private/var/tmp/_bazel_marvin/9cf0c27c2f651654c121c526ef57328f/external/crate_index__async-executor-1.8.0/BUILD.bazel
ERROR: /private/var/tmp/_bazel_marvin/9cf0c27c2f651654c121c526ef57328f/external/crate_index__surrealdb-core-1.3.1/BUILD.bazel:16:13:
no such target '@@crate_index__async-executor-1.8.0//:executor': target 'executor' not declared in package ''
defined by /private/var/tmp/_bazel_marvin/9cf0c27c2f651654c121c526ef57328f/external/
crate_index__async-executor-1.8.0/BUILD.bazel
and referenced by '@@crate_index__surrealdb-core-1.3.1//:surrealdb_core'
It is indeed true that there is no target executor, only an async_executor.
However, there is an executor target in the benches and I wonder if the generated specs somehow mixed these up?
The SurrealDB/Core crate seems to trigger the issue. AFAIK, SurrealDB adds some 150 dependencies, and, among others, the async-executor that throws the error.
Is this a bug in the rules, or did I misconfigured something?
Is there any known workaround for this kind of undeclared error from a generated dependency?
Any help would be appriciated.
Thank you,
Marvin
I created a self-contained example to reproduce the issue:
Repo to reproduce: bazel_rust
Hi, I'm setting up a Rust mono repo with > 35 crates. I am generating all dependencies with crate_universe, exactly as described in the documentation. While configuring Bazel for the first crate, I stumbled across the following error when running bazel build
When I query the dependency in question:
bazel query "@crate_index__async-executor-1.8.0//:*"
It is indeed true that there is no target executor, only an async_executor.
However, there is an executor target in the benches and I wonder if the generated specs somehow mixed these up?
Output:
The SurrealDB/Core crate seems to trigger the issue. AFAIK, SurrealDB adds some 150 dependencies, and, among others, the async-executor that throws the error.
Is this a bug in the rules, or did I misconfigured something?
Is there any known workaround for this kind of undeclared error from a generated dependency?
Any help would be appriciated.
Thank you,
Marvin
I created a self-contained example to reproduce the issue:
https://github.com/marvin-hansen/bazel_rust
Here is the Build file:
And the WORKSPACE file:
The text was updated successfully, but these errors were encountered: