-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Unable to use build_event_stream.proto as external dependency #16335
Comments
Adding the similar bug #15874. Not the dupe. |
Seems very similar to bug #15874, so assigning to its team. |
Indeed #15874 sounds similar, thanks @sgowroji for noting the connection! @JSGette, why do you want to consume all the required proto files? Would instead consuming an appropriate |
@michaeledgar fyi |
I also need this to be visible. Mine is |
@haxorz I wanted to consume this target: |
Related to #3684. Possibly even a dupe. |
I had this same issue today trying to make something that would consume BEP and make the appropriate output for github actions. |
This looks easy to correct. I'll check around for some historical context, but AFAICT this seems like a totally fine change to make: https://bazel-review.googlesource.com/c/bazel/+/238093 I'm not terribly persuaded that the BEP protobufs need to live in a different repository, though perhaps they belong with the other protobufs. |
This makes the build event stream and starlark debugging proto libraries public. This is for consumption by the vscode-bazel plugin, which already uses these but in a very hacky way. Fixes bazelbuild#16335 Fixes bazelbuild#3684
This makes the build event stream and starlark debugging proto libraries public. This is for consumption by the vscode-bazel plugin, which already uses these but in a very hacky way. Fixes bazelbuild#16335 Fixes bazelbuild#3684 Closes bazelbuild#21196. PiperOrigin-RevId: 623740758 Change-Id: Ic47d6dd05fcf2af8beec4d9212d4c7fd65bcda44
This makes the build event stream and starlark debugging proto libraries public. This is for consumption by the vscode-bazel plugin, which already uses these but in a very hacky way. Fixes #16335 Fixes #3684 Closes #21196. PiperOrigin-RevId: 623740758 Change-Id: Ic47d6dd05fcf2af8beec4d9212d4c7fd65bcda44 Commit adfe016 Co-authored-by: Cameron Martin <[email protected]>
This makes the build event stream and starlark debugging proto libraries public. This is for consumption by the vscode-bazel plugin, which already uses these but in a very hacky way. Fixes bazelbuild#16335 Fixes bazelbuild#3684 Closes bazelbuild#21196. PiperOrigin-RevId: 623740758 Change-Id: Ic47d6dd05fcf2af8beec4d9212d4c7fd65bcda44
A fix for this issue has been included in Bazel 7.2.0 RC1. Please test out the release candidate and report any issues as soon as possible. |
Description of the bug:
Instead of putting build_event_stream.proto directly into my project to implement build event service I want to consume all required proto files by putting bazel as external dependency in WORKSPACE file of my project:
Content of external/bazel.BUILD:
This doesn't work as in BUILD default visibility is defined to subpackages of src package within bazel.
Hence, it isn't possible to access proto-files directly without "patching" cloned repository and removing BUILD file.
Error:
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
WSL2 (Ubuntu)
What is the output of
bazel info release
?release 5.3.1
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD
?No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: