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
In a cargo setup, when a proc macro crate is present in a cargo workspace, and one of the crates in the workspace depends on the proc macro crate, dependencies fail to resolve with the following error:
Error in fail: /home/developer/.cache/bazel/_bazel_developer/2927fffaf2126be7f97bf2508c6daa6e/modextwd/rules_rust~~crate/cargo-bazel splice --output-dir /home/developer/.cache/bazel/_bazel_developer/2927fffaf2126be7f97bf2508c6daa6e/modextwd/rules_rust~~crate/crates/splicing-output --config /home/developer/.cache/bazel/_bazel_developer/2927fffaf2126be7f97bf2508c6daa6e/modextwd/rules_rust~~crate/crates/config.json --splicing-manifest /home/developer/.cache/bazel/_bazel_developer/2927fffaf2126be7f97bf2508c6daa6e/modextwd/rules_rust~~crate/crates/splicing_manifest.json --cargo-lockfile /workspace/rust/Cargo.lock --cargo /home/developer/.cache/bazel/_bazel_developer/2927fffaf2126be7f97bf2508c6daa6e/external/rules_rust~~rust_host_tools~rust_host_tools/bin/cargo --rustc /home/developer/.cache/bazel/_bazel_developer/2927fffaf2126be7f97bf2508c6daa6e/external/rules_rust~~rust_host_tools~rust_host_tools/bin/rustc returned with exit code 1:
Blocking waiting for file lock on package cache
Updating crates.io index
error: no matching package named <the proc macro crate's name> found
location searched: registry `crates-io`
required by package `rules_rust_fake_proc_macro_root v0.0.0 (/tmp/.tmp79Nulh)`
Error: Failed to generate features
Caused by:
Failed to run cargo tree: exit status: 101
this error seems to happen in v0.49.1. everything works fine in v0.48.0
The text was updated successfully, but these errors were encountered:
1. Skip in-workspace proc-macros - they shouldn't be resolved, and are
already resolve roots
2. Properly parse out git deps, rather than assuming everything is a
registry dep
Fixes#2777Fixes#2783
In a cargo setup, when a proc macro crate is present in a cargo workspace, and one of the crates in the workspace depends on the proc macro crate, dependencies fail to resolve with the following error:
this error seems to happen in v0.49.1. everything works fine in v0.48.0
The text was updated successfully, but these errors were encountered: