Hi guys, we have some problem with this, i cant start my space again:
2 Likes
So I did refactory build to work but i think we have some problem with cpu space when it enter in sleep mode, lets wait next turn.
1 Like
It wasn’t my Spaces, but I encountered a similar case a few days ago.
- Even after pausing Spaces or performing a normal rebuild, the previous runtime persisted as a ghost (accessible and functional via API)
- If a ghost exists, the build completes but the app won’t launch anew
- Only a factory rebuild could eliminate the ghost runtime
- After that, it started working fine
So as a “folk remedy”: If you’re stuck, try a factory rebuild → If that fails, try a rebuild with an empty commit → If that fails, change sdk in README.md and revert it to clear the cache
1 Like
This is a recurring error, and I think it deserves to be investigated and corrected, because all the CPU space, once it enters sleeping mode, is not returning to active status when the visitor requests that it be woken up, now this repo Gradio Video Slider - a Hugging Face Space by elismasilva @hysts
1 Like
Yeah. I don’t think it happened much before, too…
Link: Another ongoing infrastructure issue (unsure related or not):
Hi @elismasilva
Thanks for flagging this. We can reproduce the 500 error when trying to wake the Space.
At the same time, looking at the account, it seems there are currently 19 cpu-basic Spaces running. Since we introduced a limit a few months ago on how many cpu-basic Spaces can run concurrently, I would have expected a quota-related message to appear once that limit was reached.
Are you seeing any quota limit message when you create a new cpu-basic Space? If not, there may be something unexpected going on here, and we can look into it further.
1 Like
The original issue in that thread was caused by a DDoS-related incident and has already been resolved. The behavior also looks different, so it does not seem related to this case.
1 Like
I see. Got it.