Fabian Meumertzheim
Fabian Meumertzheim
@bazel-io fork 7.3.0
@bazel-io fork 7.4.0
I would say this is working as intended: In WORKSPACE mode, Bazel has always provided default definitions for certain repos, including `rules_cc`. This logic is still active for backwards compatibility...
I'm seeing this every single time on Bazel 8. https://github.com/bazelbuild/bazel/issues/25076 has a similar jstack and also the requested `java.log`.
@keith Does it do so with `--verbose_failures`?
@bazel-io fork 7.2.0
@joeleba Should we `@bazel-io flag` this for Bazel 7? Interestingly Bazel itself depends on source files in `.git` at https://github.com/bazelbuild/bazel/blob/07a571f70beed3fc46c14b4c933db91e79cfdb80/BUILD#L54-L61. The minimal solution of not symlinking just `.git` may thus...
Could this be realized by a third-party Starlark library that either 1) downloads the Chicory JAR and executes it with Bazel's embedded JDK (slight hack) or 2) downloads a Graal...
> And downloading a native WASM interpreter wouldn't provide much benefit over simply downloading natively-compiled versions of a repository generator tool, with similar downsides with regards to portability. Yes, this...
@sdtwigg Has this been solved by https://bazel.build/reference/command-line-reference#flag--local_extra_resources?