Fabian Meumertzheim
Fabian Meumertzheim
Having the BCR modules also provide the Go targets is somewhat useful since it avoids version skew between the protos (coming from the Bazel module) and the generated Go code...
This being difficult to fix in Bazel 7 was exactly the motivation for the change in Bazel 8 that doesn't watch all `Label`s passed to `module_ctx.path`. You could add a...
https://github.com/bazelbuild/bazel/commit/50196979346cb57bc2e239d8bcd5342d4000292e added the incompatible flag and yes, it also applies to the repo rule context.
This isn't specific to Go. Path mapping requires a sandboxed execution mode, which on Windows only leaves remote execution (and sandboxed multiplex workers).
I'll pick up work on https://github.com/bazelbuild/bazel/pull/25430 again.
This has been fixed in Bazel (https://github.com/bazelbuild/bazel/commit/a42c98185717661c5425aa4161289381f4811c9c).
@bazel-io fork 7.4.0
Closing in favor of #23750
@bazel-io fork 7.4.0