Spaces:
Running
on
A10G
Build error on A10G/torch error
I cloned MusicGen for my own project and I'm getting a build error. I just re-cloned it recently and not sure what is going on with this? It looks like the main FB MusicGen is crashed too. Gradio has been consistently unstable too, with my clones. Whassup?
I'm getting this build error on mine:
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'error'
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [6 lines of output]
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "/tmp/pip-install-9fe_hde8/xformers_9d4dc20c2b994550969be2e917f0c575/setup.py", line 18, in
import torch
ModuleNotFoundError: No module named 'torch'
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
Hey @MantraDas ! Thanks for reporting! Could you please try cloning the space again with the new requirements file? Following the commit a8c11a7 we should have torch installed correctly
Yeah it works now, thank you!
But now I'm getting "error connection timed out" a lot more frequently. Testing it again on a different computer. Are y'all getting connection timeouts?
I'm having GRADIO problems again too. The processing goes to 100% but then gradio is a big black box that won't let me download the file. Happens a lot, even with easy prompts.
:(
Hey @MantraDas - the Space is working for me on the Chrome browser. Could it be a browser error stopping the playback? Chrome seems to work best for me for playing multimedia outputs, so it's worth a try here
I'm using Chrome but it's on a Chromebook, which is kind of old-ish. It could very well be the browser, but it seems to happen about 20% of the time and not consistently. It's not that big of a deal, but I am wondering why it keeps happening instead of working consistently. I'll try to dig around in the logs. Thank you for helping to support this incredible project!
OK- I tested it on my Windows computer that has pretty good specs, and still getting this error about 70 percent of the time:
Something went wrong
Connection errored out.
I don't know where the logs are found to look at it them, and I'm using pretty easy prompts that are like 5 words long. It seems like the recent update fixed the GRADIO problem but then connection errors keep happening. Is anybody else having this problem? I'm doing 120 second exports so maybe that's too long for it to handle?
From what I've been seeing, if the Windows screen lock happens, then it puts the music generation in an error state. But then refreshing the page and trying to generate a new audio rendering ends up as queued because the rendering is still somehow happening on the VM even though the front-end has errored out. The error frequently happens with or without the screen lock though. I wonder what is going on.