-
Notifications
You must be signed in to change notification settings - Fork 81
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 rules_haskell in Bazel 7.0 #1846
Comments
Hi @ylecornec, Can you share any significant update on this issue. Thanks! |
This was referenced Jun 19, 2023
Merged
Merged
Hi @ylecornec, We are still seeing few failures for the above incompatible flag in the pipeline. Can you please have a look Thanks!
|
Hi @sgowroji. How is this IOException related to the incompatible flag? Also the CI run you linked to seems to be green. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Incompatible flag
--incompatible_disable_starlark_host_transitions
will be enabled by default in the next major release (Bazel 7.0), thus breaking rules_haskell. 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: