Skip to content
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

Keep getting this error #276

Open
refreshedcyberjohn opened this issue Mar 8, 2023 · 7 comments
Open

Keep getting this error #276

refreshedcyberjohn opened this issue Mar 8, 2023 · 7 comments

Comments

@refreshedcyberjohn
Copy link

So whenever I run the V2 notebook on Colab, it keeps giving me this error:
error: subprocess-exited-with-error

× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.
Building wheel for llvmlite (setup.py) ... error
ERROR: Failed building wheel for llvmlite
Running setup.py clean for llvmlite
Successfully built jukebox fire librosa numba mpi4py
Failed to build llvmlite
Installing collected packages: llvmlite, unidecode, tqdm, numba, mpi4py, fire, soundfile, resampy, librosa, jukebox
Attempting uninstall: llvmlite
Found existing installation: llvmlite 0.39.1
Uninstalling llvmlite-0.39.1:
Successfully uninstalled llvmlite-0.39.1
error: subprocess-exited-with-error

× Running setup.py install for llvmlite did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.
Running setup.py install for llvmlite ... error
WARNING: No metadata found in /usr/local/lib/python3.9/dist-packages
Rolling back uninstall of llvmlite
Moving to /usr/local/lib/python3.9/dist-packages/llvmlite-0.39.1.dist-info/
from /usr/local/lib/python3.9/dist-packages/~lvmlite-0.39.1.dist-info
Moving to /usr/local/lib/python3.9/dist-packages/llvmlite/
from /usr/local/lib/python3.9/dist-packages/~lvmlite
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> llvmlite

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.

ModuleNotFoundError Traceback (most recent call last)
in
6 get_ipython().system('pip install --upgrade git+https://github.com/craftmine1000/jukebox-saveopt.git')
7
----> 8 import jukebox
9 import torch as t
10 import librosa

ModuleNotFoundError: No module named 'jukebox'


NOTE: If your import is failing due to a missing package, you can
manually install dependencies using either !pip or !apt.

To view examples of installing some common dependencies, click the
"Open Examples" button below.

What is going on?

@arkaneskye
Copy link

I'm getting this too, nothing seems to work, manually installing dependencies seems to cause more problems

@Broccaloo
Copy link

All Colab notebooks for Jukebox were broken because Colab upgraded to Python 3.9.

The jukebox-saveopt repo, which is used by the One-Click V2 notebook you mentioned has been fixed already, so everything should be back to normal there. https://colab.research.google.com/drive/1sJda9v46gNzBc7m59MP5zn63AWc-axCY?usp=sharing

As for all notebooks that use the official repo, they are still broken. I'm doubtful whether OpenAI wants to fix this, considering there haven't been updates for years.

@refreshedcyberjohn
Copy link
Author

refreshedcyberjohn commented Mar 10, 2023

Oh, I see, and it works now.

@clearsitedesigns
Copy link

How did you get it to work? I still see the same issue.

@Broccaloo
Copy link

How did you get it to work? I still see the same issue.

As I mentioned above, all notebooks that use the standard repo are still broken. You can use my fork instead, where the issue is fixed https://github.com/Broccaloo/jukebox

@240db
Copy link

240db commented Mar 17, 2023

Thanks for the information Broccaloo, btw your samples with jukebox are super awesome, thanks for sharing the repo and the notebook!

@Byron-Zoomry
Copy link

can we install your fork locally? Installation instructions seem to be the same as the main repo and I get that pesky mpi error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants