-
Notifications
You must be signed in to change notification settings - Fork 113
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
target <target @@hedron_compile_commands//:_refresh_all> does not have rules_python PyRuntimeInfo or builtin PyRuntimeInfo #163
Comments
Hi, @axbycc-mark! Thanks for giving the tool a try and for writing in. I....am not sure based on that description and haven't been able to reproduce it on my machine. One guess if you're importing via the workspace: Could you try bringing in this tool first (rather than at the end of the file)? My first guess is that maybe some other dependency is bringing in an old version of rules_python. If that doesn't work, could I ask you to explore some more and maybe give me some more details? Thanks, |
I found out the error occurs even in an otherwise empty project, which I have uploaded below. https://github.com/axbycc-mark/hedron-compile-commands-repro/tree/master Is it because I am using a WORKSPACE file instead of using the new module system? Thanks for your help, I am excited to get this working! |
Phew, yikes. Thanks @axbycc-mark. I'm guessing it must be a Windows-specific bazelbuild/rules_python issue, then, since that test project runs cleanly on Mac and the error doesn't seem to make a lot of sense...it's rules_python complaining about it's own py_binary rule? Here's what I think we should do: Would you be down to report this to the folks over at bazelbuild/rules_python, cc me? (It looks like they've got other windows breakages over there....) Then would you be down test with rules python downgraded (use this tool's commit 4d56714)? If that works, great, temporarily. And if not let's zip you back to 6d58fa6, just to make sure all was working before moving to rules python. I'm so sorry this has caused a headache; we tried to switch to Bazel's new python infrastructure to not reply on system python and to be able to use packages, but they've had quite a few bugs. |
4d56714 failed with the same error.
I hope that helps. |
Not sure what to put for the python_rules version in my upstream issue, can you let me know? |
Thanks so much for reporting and helping. Replied over there. Sorry again about the headache here. Importance of that test case I was asking you to run is to make sure they aren't just wholly broken on windows. We'll knock this out if we work together :) |
Mostly reverts 0e5b1aa Tracking restoration at #168 Please see - #163 - bazelbuild/rules_python#1732 - #165 - (rules_python issue to come) - #166 - bazelbuild/rules_python#1169
Reverted rules_python in 0b821b7. Tracking restoration in #168. That avoids this for now, but seriously, worth our working with them to get it fixed for future use; this'll be important in the future. (Just holler if you want me to reopen.) Thanks again for helping leave things better than you found them! |
Mostly reverts hedronvision/bazel-compile-commands-extractor@59dc7ff Tracking restoration at hedronvision/bazel-compile-commands-extractor#168 Please see - hedronvision/bazel-compile-commands-extractor#163 - bazelbuild/rules_python#1732 - hedronvision/bazel-compile-commands-extractor#165 - (rules_python issue to come) - hedronvision/bazel-compile-commands-extractor#166 - bazelbuild/rules_python#1169
Following the setup, I ran
bazel run @hedron_compile_commands//:refresh_all
and got this errorBazel version 7.0.2
Windows 10 x86_64
The text was updated successfully, but these errors were encountered: