-
Notifications
You must be signed in to change notification settings - Fork 20
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
Bazel examples failing to build due to obscure python deps error #228
Comments
Thanks for reporting this issue! Can you confirm it is still happening at the repository HEAD? There were some fixes checked in past v0.3.2, but they haven't yet been incorporated in a new release. |
Yes, I can confirm. I created my own release here pointing to HEAD: And received the same issue. Only thing I changed was default clang toolchain because I didn't want to install clang10, but this should be unrelated to the problem. |
Also of note, this command (referenced in the above error output):
when I run manually succeeds, so this must be failing in the bazel environment somewhere. |
I hit this too. The relevant error seems to be: Which seems to be a problem with python 3.11 and the importlib_metadata package. |
The following is a workaround that worked for me:
|
Thanks! As an aside, I was also able to workaround this with
I'm sure local will work if you use conda or venvs. |
Any plans to support python 3.10 or later? Ubuntu 24.04 ships with python 3.12 by default and throws a similar dependency error (cc @fmeum). |
@florianGla What is the exact error you are seeing and what's the command you ran to get it? I just verified that I can run all the examples just fine in a Docker container with Ubuntu 24.04, clang 18 and Python 3.12. |
Expected Behavior
rules_fuzzing
examples work "out of the box" (after installing dependencies of course)Actual Behavior
Examples are not working and are failing due to some strange python error.
Steps to Reproduce the Problem
git clone git@github.com:bazelbuild/rules_fuzzing.git && cd rules_fuzzing
bazel build //examples:empty_fuzz_target
This results in the following error:
This seems to be a pip issue? For the record, I also forked and created a release from HEAD since I saw that
rules_python
and installation steps were updated, however following the latest commit did not resolve the problem either.Things I've tried
rules_python
Specifications
rules_fuzzing-0.3.2
bazel-5.4.0
Python 3.11.3
pip 23.1.2
clang 15.0.7
Manjaro Linux 6.1.31-2-MANJARO
The text was updated successfully, but these errors were encountered: