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
ERROR: /private/var/tmp/_bazel_user/b8286dc79fef4b6257e32e451f5cae57/external/rules_rust+/crate_universe/extensions.bzl:833:37: Traceback (most recent call last):
File "/private/var/tmp/_bazel_user/b8286dc79fef4b6257e32e451f5cae57/external/rules_rust+/crate_universe/extensions.bzl", line 949, column 59, in _crate_impl
cargo_path, rustc_path = _get_host_cargo_rustc(module_ctx, host_triple, cfg.host_tools_repo)
File "/private/var/tmp/_bazel_user/b8286dc79fef4b6257e32e451f5cae57/external/rules_rust+/crate_universe/extensions.bzl", line 833, column 37, in _get_host_cargo_rustc
cargo_path = str(module_ctx.path(Label("@{}//:bin/cargo{}".format(host_tools_repo, binary_ext))))
Error in path: Unable to load package for @@[unknown repo 'my_rust_host_tools' requested from @@rules_rust+ (did you mean 'rust_host_tools'?)]//:bin/cargo: The repository '@@[unknown repo 'my_rust_host_tools' requested from @@rules_rust+ (did you mean 'rust_host_tools'?)]' could not be resolved: No repository visible as '@my_rust_host_tools' from repository '@@rules_rust+'
ERROR: error evaluating module extension @@rules_rust+//crate_universe:extensions.bzl%crate
It's important that consumers of crate_universe are able to easily describe the version of rust their generation is based off of. Ideally there would be a rust_version attribute on from_cargo and from_specs but I don't know if this is the most performant path. Suggestions welcomed!
The text was updated successfully, but these errors were encountered:
It's currently not possible to define a custom version of Rust for crate universe extensions
This will fail with the following error
It's important that consumers of crate_universe are able to easily describe the version of rust their generation is based off of. Ideally there would be a
rust_version
attribute onfrom_cargo
andfrom_specs
but I don't know if this is the most performant path. Suggestions welcomed!The text was updated successfully, but these errors were encountered: