Jesse Schalken

A specific use case that is broken by this is embedding a `js_binary` in a Linux container image with `rules_docker` or `rules_oci`, but building on macOS or Windows, or Linux...

> I'm surprised we haven't heard similar issues with py_binary, I think it's the same setup? [py_runtime](https://bazel.build/reference/be/python#py_runtime) doesn't contain a label to a `cc_library` like `node_toolchain` does, so doesn't have...

One option would be 1. Use a `filegroup` instead of a `cc_library` 2. Include just a `DeafaultInfo` of the header files in the `NodeInfo`, instead of a `DefaultInfo` and a...

@alexeagle Have you considered downloading the archive with `http_file`/`rctx.download` and then doing the untar in a build action and consuming the untarred directory in downstream actions? So it stays as...

@alexeagle Alternatively to avoid doing an untar in a build action, you could `glob(["**/*"])` up all the inputs and use `copy_to_directory` to turn them into a single directory and expose...

> Rules outputting directories (which is not sane, but unfortunately happens) @SanjayVas I believe this is referring to rules which do `ctx.actions.declare_file` during analysis but then create a directory during...

IMO in the absence of another fix this is a good change to have behind an option (eg an environment variable to pass with `--repo_env`). The many "dependency checking of...

@fmeum Yep that would also work, I don't think I will be able to spend any more time on this for a while though.

This is similar to an issue we found in `rules_go`: https://github.com/bazel-contrib/rules_go/issues/4127. Bazel resolves the execution platform per target, per configuration, so you can't reliably pass information about "the" exec platform...

We are running into this as well. We have tests tagged with `no-remote-exec` because they are incompatible with remote execution, and aspects that register their own validation actions, and we...