Hmm… The cause may sometimes be a specification change by Hugging Face, but more often it occurs because the contents of the “latest version” of libraries specified in requirements.txt change over time. Anyone can modify requirements.txt in duplicated space, but it requires knowledge or searching…
A feature like “duplicate the space while fixing the library versions to those from the last successful startup” would help a bit… But structurally, this might be difficult.
Well, if it’s a simple error in Zero GPU Spaces, I can probably suggest a fix if you ask me…
User-to-user mutual aid is good, but for paid services, it would be even better if HF had a dedicated support channel.
Edit:
For the IDM_VTON space, since large files are included in the repository, this scenario might also apply. Essentially, splitting Spaces into Spaces and Models will resolve the issue. However, it requires a few lines of coding.
In any case, the root cause, broadly speaking, is that “the environment has changed since the space was first launched normally, causing behavior change of the code” If adapting code to the current environment manually will make it work. There are few exceptions, but they are rare.