John Firebaugh

It would change the execution environment of the code that the runner is running, which may be expecting the current directory to be the one where the command was executed.

I haven't seen it. I think closing this issue is appropriate.

I switched to rules_js, which doesn't have this issue.

That would make it incompatible with debugging in VSCode using a plugin like [CodeLLDB](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb). Is there some reason the `macos_application` rule can't provide a `FilesToRunProvider` whose executable points to an...

Discussion [here](https://bazelbuild.slack.com/archives/CA31HN1T3/p1670005824438539), but the gist of it is this probably isn't currently possible because there's no way within Starlark to construct a `File` that refers to a child of a...

Not stale.

There's an unstable JUnit formatter built in to libtest. Tracking issue: https://github.com/rust-lang/rust/issues/85563

This was fixed by https://github.com/bazelbuild/rules_rust/pull/1444.

I'm inclined to keep it simple. Do any other mapping libraries use this alternative definition?

Want to submit a PR with an example containing the above code?