David Marcin

The problem here was that `get_current_span()` did not actually need to be unsafe and somehow the proc macro "knows" this and chokes on it, but doesn't give a very good...

Would setting `NODE_PATH` in the linker script be an option? I tried to hack it in but it seems like it fails soon after because this path is expected to...

Even after hacking the system to avoid making these directories read-only on the remote worker, the action still fails soon after because of this error: ``` ERROR[runfiles.bash]: cannot look up...

Passing `--extra_rustc_flags` to `CARGO_ENCODED_RUSTFLAGS` certainly seems reasonable to me from [the description](https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-build-scripts). I don't have context on why `--extra_exec_rustc_flags` wasn't passed to `cargo_build_script`, but the reason `--extra_rustc_flags` was not is...

Specifically, this is a problem when using remote execution. When executing locally, it works, so it is probably finding stdarg.h via some undeclared inputs. I have a hacky workaround where...

I tried both with and without a custom toolchain and they both exhibited the issue.

I think what makes this issue different from the linked issue is that remote execution only works if all inputs from the execroot are declared, whereas local execution can get...

When you say "you need to" that implies that this isn't just broken with the base `rules_rust` -- it is. I agree that the problem is likely that the rust_bindgen_toolchain...

I'm trying to cross-compile from macOS intel -> macOS arm64. I had to set up this `rust_repository_set` in `WORKSPACE`: ``` rust_repository_set( name = "rust_darwin_aarch64_cross", exec_triple = "x86_64-apple-darwin", extra_target_triples = ["aarch64-apple-darwin"],...

🤦 This error is caused because I needed to specify `edition = "2018"` on the rust_repository_set. Otherwise this seems to work. I am still curious why `rules_rust` does not declare...