Closed sgowroji closed 1 day ago
This failure is caused by Bazel 8 prereleases pulling in protobuf-27.x or 29.x (and overriding the perfectly good protobuf 21.x that stardoc requests). The newer versions of protobuf are incompatible with Bazel 8 because they try to use native.py_* symbols.
Unfortunately, the fix needs to come from Bazel. Specifically:
And until above is done, Stardoc users are broken on Bazel 8 :/
@Wyverald @comius - correct me if I am wrong on any of these points.
@comius - note that Bazel's https://github.com/bazelbuild/bazel/blob/master/third_party/protobuf/add_python_loads.patch fixes the protobuf module used by Bazel to build itself, but doesn't fix the protobuf module loaded by external users of Bazel who depend on \@bazel_tools.
For stardoc and anyone who depends on stardoc transitively, the Bazel 8-compatible version of protobuf needs to be in BCR.
Fixed by #263
CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4198#01928934-6200-4035-af00-d045db026e38
Platform: Windows
Logs:
Culprit:
Steps:
CC Greenteam @meteorcloudy