Xùdōng Yáng
Xùdōng Yáng
Could you rebase the PR to HEAD and try the checks again? The cc_coverage thing might have been fixed already.
FYI this turned out to be rather hard to merge, since it interacts negatively with some internal systems. With all the scrambling going on before the 6.0 cut, I haven't...
Unfortunately it's not that easy. There's a long-running service that Google uses to answer large scale Blaze queries, and its protocol definition sticks to the default value of the flag,...
i had a similar thought to Cameron's actually. The `toolchain` rules (not the `rust_toolchain` rules) are kind of already "pointer" rules. Maybe we can afford to have those in the...
This is a long-standing known bug in Bazel which IIUC unfortunately does not have a short-term solution. The migration of AOSP onto Bazel encountered similar problems. @lberki could you comment...
We could flip after 6.0 of course; just need an owner to watch out for downstream breakages and coordinate fixes. Just for my curiosity, wouldn't there still be some sort...
Given the number of release blockers present and the unresolved redness in the downstream pipeline, we'll tentatively push out the branch cut date by two weeks (to 2022-09-26).
There are still many release blockers outstanding (most importantly #16124 and #10298), we're going to push the branch cut date by another two weeks (to 2022-10-10).
@bazel-io fork 5.3.1
The fix introduced a regression (see https://github.com/bazelbuild/bazel/pull/16008#issuecomment-1224267553), which we will probably need a patch release for.