-
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
RTX failed to build nanoset package #540
Comments
Update: I was able to circumnavigate (for my own code) the issue by individually type out pip install for each package listed in requirements.txt. However, I'm still not sure why when I typed pip install -r requirements.txt, it not only installed the packages in requirements.txt but also more stuff that requires rust. Maybe somewhere along the code there exist packages that need to use a rust compiler? |
I'm unable to reproduce this bug. On macOS 10.14.6, I just did:
no error messages, and nothing about rust. |
Can you please post a step-by-step reproducible example for this bug, along the lines of what I showed above? |
These are the command that I typed: error: aborting due to 89 previous errors For more information about this error, try Caused by: ERROR: Failed building wheel for nanoset |
dan, can you try what I did?
|
I managed to run the above, and I don't even have rust on my system:
|
Here is the output of "pip3 freeze" from the clean installation I just did:
|
@power10dan what makes you think that nanoset is dependent on pyo3? I don't see pyo3 in the output of |
So, I typed what you typed. Here is the installation thing that I got: btw, this is from https://github.com/RTXteam/RTX/blob/master/requirements.txt |
Like, I did the pip install thing on the requirements.txt from https://github.com/RTXteam/RTX/blob/master/requirements.txt |
just confirming -- you did it in a brand-new virtualenv just like I did, right? |
I'm still very confused about why pip3 is somehow invoking rustc on your system. any ideas? |
@power10dan what version of macOS are you running? |
Yup. I tried what the tutorial did, but for some reason the tutorial doesn't work, as for some reason, inside the pyo3 code that nanoset uses, it was not updated to the latest version. The latest version of pyo3 in docker fixes this issue. But I think for some reason the authors of nanoset didn't update their pyo3 to the latest version, and thus causing this issue. I am running on macOS Sierra. |
and yes, I did it in a brand-new env, and did it outside of an env. |
OK I am running on Mojave. Maybe that is the reason? |
Wait what, you are running in docker? |
Maybe check with the others in the Ramsey Lab to see if anyone else is running on macOS Sierra... to see if they have the same issue? IIRC, mac users in the lab include @amykglen , @zheng-liu, and Qi Wei. |
Nope, I'm not running on Docker. One of the solution proposed online is to use the dockerized version, but the problem lies in the nanoset package. I think I figured out why. I was retracing the stack trace, and one of the packages pip is trying to install is called nose, which is located in https://github.com/RTXteam/RTX/blob/d756bc9fbed8e14a0777952312e43f61f21e0d63/code/UI/OpenAPI/python-flask-server/test-requirements.txt I think the problem lies in the fact that I ran pip install -r requirements.txt in the root of the RTX directory. Magically, for some reason, pip decides to install the requirements.txt for the entire repo. |
Except isn't that what I did? And I got nanoset installed, with no problem. |
I think it might be because you have an older version of rust. I downloaded the newest version of rust, and the compiler was spitting out a bunch of syntax errors for multiple code segments in the nanoset source code. |
Hi guys, if we have env incompatibility issues very which are very hard to solve, I also recommend trying https://github.com/pypa/pipenv, instead of pip install. |
@power10dan , I don't think I have rust installed at all on my macOS system. See below:
Appears that I am getting a precompiled install. This doesn't seem to be an RTX bug, closing. |
When I was trying to do pip install --r requirements.txt on my macOS, nanoset fails to build. The rootcause seems to be nanoset, which is a package that is dependent on pyo3. The problem I'm having is that my rust compiler (the latest nightly build, as suggested by the pyo3 devs) failed to successfuly compile the package, and gave me a long stack trace along with "cargo failed with code 101." I don't have much ideas on how to fix it, as it's an outdated package issue rather than a code bug that we can dive in to fix it ( I could be wrong, but this is what it looks like to me). Do we really need nanoset? Also, how did you guys install rust? Did anyone of you use the rust nightly build?
The text was updated successfully, but these errors were encountered: