A few of my Spaces have been “Building” for weeks. It’s happened in the past when it’s “Building” for a few days and then I reset it and its fine. But this time around it won’t start!
I tried everything… restarting, factory rebuild, deleting files and then re-uploading, etc.
I created a new Zero GPU space and uploaded the source code, and the build itself completed.
It seems to be due to the build stack problem in Spaces that has been occurring frequently recently.
This is a phenomenon in which Spaces itself stops progressing from the build, and the same code works in a different Spaces.
We don’t know the details, such as whether there is some kind of flag or whether it is a malfunction of something like a cache.
A relatively gentle workaround is to rename the current Spaces, change the hardware to Free CPU, and save it as Private. Then, you can place the newly created Zero GPU Space in the empty space.
Ideally, it would be good if the problem could be solved properly, but in most cases like this, it takes time…
I’ve been facing the same issue since yesterday. I’ve tried all the suggested solutions, but none of them have worked. Unfortunately, I don’t have the option to change the CPU where the system is hosted.
I tried renaming and it didn’t work. I upgraded my Gradio version. I restarted the space, factory rebuild. Nothing… a lot of my spaces are experiencing this.
There aren’t any fixes yet?
This problem has not been fixed for a long time. There may be more than one cause.
Also, renaming is not an option. Unless you create a completely new Spaces, the disease will continue…
Re-upload the source code only.
Bummer hopefully there is a fix in the future. @geronimo-pericoli you still experiencing the same problem?
Just wanted to check in and see if there are any fixes. I have so many spaces that are permanently building.
Just wanted to follow up one more time.
It is still occurring, and the workaround is to recreate the Space, but the solution is unknown… @meganariley
This happens to me sometimes when the space tries to load to a port that isn’t 7860.
Flask will do 5000 unless told to launch on port 7860.
Sometimes need to do docker and nginx.conf to reverse proxy to port 7860.
I see your app.py is
import os
exec(os.environ.get('APP'))
Check which port it’s aiming at if you haven’t debugged this part yet.
so, I guess 7860 applies to Gradio and Docker SDK space
port 8501 for Streamlit space
Only port 8501 is allowed for Streamlit Spaces (default port). As a result if you provide a `config.toml` file for your Space make sure the default port is not overridden.