-
Notifications
You must be signed in to change notification settings - Fork 512
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
refactor: toolchainize py_proto_library #1577
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Not ready yet; waiting for bazelbuild/rules_proto#194 to gate this feature. |
fixes #1080 consequently. |
thesayyn
force-pushed
the
toolchainize_py_proto
branch
from
December 5, 2023 00:15
04eaf58
to
7128428
Compare
ar3s3ru
reviewed
Dec 7, 2023
Relies on bazelbuild/rules_proto#207 landing and being available in a rules_proto release.
It has a bug with bzlmod where it tries to reference the label of the users toolchain_type, leading to an error like com.google.devtools.build.lib.packages.BuildFileNotFoundException: no such package '@@[unknown repo 'rules_python' requested from @@rules_proto~]//python/proto': The repository '@@[unknown repo 'rules_python' requested from @@rules_proto~]' could not be resolved: No repository visible as '@rules_python' from repository '@@rules_proto~'
alexeagle
force-pushed
the
toolchainize_py_proto
branch
from
March 19, 2024 00:36
abfdd9c
to
89f0a56
Compare
Okay this is green now. had to rename the workspace because bazelbuild/bazel#18683 (comment) |
alexeagle
approved these changes
Apr 11, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thanks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enables use of
--incompatible_enable_proto_toolchain_resolution
flag that launched in Bazel 7. This allows users to choose a pre-builtprotoc
or use the runtime from https://pypi.org/project/protobuf/ rather than be forced to use hard-coded values in Bazel core.This change is also happening in other language rulesets that provide first-class protobuf support, e.g.
bazelbuild/rules_go#3895
No update to CHANGELOG.md in this PR as the feature is not yet documented for end-users, this just makes it possible to enable the flag. A follow-up PR will provide user instructions.