Spaces:

---

VAST-AI

/

MIDI-3D

like 12

Running on L4

@akhaliq @multimodalart

@hysts Urgently need help!

@huanngzh Hmm, weird. I believe I assigned L4 earlier. Anyway, I re-assigned L4 to this Space.

I just checked the internal log and confirmed that we indeed assigned L4 earlier. Since there are two identical grant requests in the log but only one request in this Space now, it seems that you deleted the granted Space once, recreated a new one, and then submitted a new grant request. To avoid confusion, please refrain from doing this in the future.

Sorry that we changed a template and re-create this space.

In addition, I would like to ask if there are any internal logs that can help debug this space. It seems to be stuck in the starting phase. It seems difficult to solve based only on logs I've seen.

I don't think we have any logs regarding the issue, but even if we do, I don't have access to them. Anyway, I'll see if I can resolve it.

Why does this Space use docker as SDK?
Also, are you trying to build Python packages at startup time?
https://huggingface.co/spaces/VAST-AI/MIDI-3D/blob/e496f22076bc587836013dd8e1fbaabf518d728a/Dockerfile#L6-L9
https://huggingface.co/spaces/VAST-AI/MIDI-3D/blob/e496f22076bc587836013dd8e1fbaabf518d728a/Dockerfile#L44-L47

BTW, why does this Space use gradio==4.44.1? Doesn't it work with the latest 5.20.1?

@huanngzh
Adding this to your Dockerfile should fix the issue.

ENV GRADIO_NUM_PORTS=1 \
    GRADIO_SERVER_NAME=0.0.0.0

Regarding this, you can just do this:

CMD ["python", "app.py"]

I tested it by duplicating your Space:

Thanks a lot. BTW, we did not use gradio SDK because the necessary package torch-cluster can not be correctly installed, showing error like "no module named torch". Are there any suggestions?

Hmm, that's weird. I'll look into it as well.