UebelAndre
UebelAndre
I made https://github.com/rust-lang/cargo/issues/8888
But https://github.com/rust-lang/cargo/issues/8888 got closed as a duplicate of https://github.com/rust-lang/cargo/issues/1545 so that should be the tracking upstream issue.
Is [`RunEnvironmentInfo`](https://bazel.build/rules/lib/RunEnvironmentInfo) available to starlark rules somehow?
I've tried to implement this feature but it seems to require quite a bit of plumbing and I think (as someone who has zero familiarity with the Bazel code base)...
@fmeum sorry for the delay. Seems you've run into this issue too?
So how should it be implemented? Do you have bandwidth to work on this?
re https://github.com/bazelbuild/bazel/issues/16076#issuecomment-1242961552 I think this sounds good. This provider though wouldn't have any impact on actions though, right? `RunEnvironmentInfo` would only affect `run` and `test` invocations. If one wanted arguments...
Any word from @comius on this? Do I understand correctly that progress is blocked on gaining consensus for the design?
Hello, would it be possible to cherry-pick https://github.com/bazelbuild/bazel/commit/9c98120f33579b72561e02826d9fccf222eccb3c (https://github.com/bazelbuild/bazel/issues/15130) for `5.3`?
I've got it working on my mac using zsh but it's painfully slow. Are others experiencing the same?