-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flag --incompatible_disable_starlark_host_transitions will break Cloud Robotics Core in Bazel 7.0 #95
Comments
Hi @ensonic, Could you please look into this issue and share any significant update. Thanks! |
We're trying to port from rules_docker to rules_oci (see #130), but have trouble finding a good replacement for:
see https://github.com/googlecloudrobotics/core/blob/main/bazel/app_chart.bzl#L1 WIP PR: #163 Any ideas? |
I had a look at rules_oci and found that it reads the digest from a file Is that file generated for the images in #163? Can we adapt our rules to read the digest from index.json? |
The only pending migration:
|
Tested with `bazel build --incompatible_disable_starlark_host_transitions //...`. Fixes #95. These aren't the newest rules_go/gazelle because of bazel-contrib/rules_go#3625.
Tested with `bazel build --incompatible_disable_starlark_host_transitions //...`. Fixes #95. These aren't the newest rules_go/gazelle because of bazel-contrib/rules_go#3625.
Incompatible flag
--incompatible_disable_starlark_host_transitions
will be enabled by default in the next major release (Bazel 7.0), thus breaking Cloud Robotics Core. Please migrate to fix this and unblock the flip of this flag.The flag is documented here: bazelbuild/bazel#17032.
Please check the following CI builds for build and test results:
Never heard of incompatible flags before? We have documentation that explains everything.
If you have any questions, please file an issue in https://github.com/bazelbuild/continuous-integration.
The text was updated successfully, but these errors were encountered: