Xùdōng Yáng
Xùdōng Yáng
As @andyrinne12 pointed out, this is fixed on HEAD. The fix is not trivial to cherry-pick back to 5.3.0, so we might just ask you to test with `last_green` instead....
I think we could actually allow `load` for top-level projects (a.k.a root modules) only. I'm also somewhat partial to the include/import solution in favor of `load`ing a macro, since using...
That would mean that registries also need to store more files than just MODULE.bazel, which I would really like to avoid.
Hmm, indeed -- that's actually an argument in favor of "import" vs "load a macro and call it".
After some implementation work and discussion, I don't think this is feasible. The gist of the problem is that segmenting the file gives the impression that each file can function...
Thanks for the very detailed report! I'm acutely aware of this -- and unfortunately this is not trivial to fix. The underlying reason is that the label `@//foo:bar`, when stringified,...
There's unfortunately no easy band-aid solution that I can think of -- using a Bazel version pre-https://github.com/bazelbuild/bazel/commit/b21069fd6f2440f90c57014b90063760223777e0 could be fine for you, though it might reintroduce the fixed bug and...
Gerrit bug: https://bugs.chromium.org/p/gerrit/issues/detail?id=14557
This seems to have been fixed.
This started failing again: https://buildkite.com/bazel/bazel-toolchains/builds/23838#58641906-6b5e-4656-a812-893c5982d2cf It was passing from 2021-01-07 to 2021-01-21. Could very likely be due to new Bazel releases? (4.0 was just released yesterday.)