It was fine until just now, but now I’m probably stuck with the same error.
It’s in the build forever.
There was no sign of anything, and another private space (also a Zero GPU space) is in the same situation.
Restarts and factory rebuilds make no sense. It doesn’t seem to reach the contents of the user’s sources, and it doesn’t seem to make sense to change the sources either.
However, the other spaces that are not running builds are all running without any problems.
P.S.
I had to try to debug it because it was buggy.
- I created a new Zero GPU space and put the same source code there, and it built and worked fine.
- I changed the hardware of the space that was being built forever from Zero GPU space to CPU space and it worked.
- When I changed the hardware back, it went back to building forever again.
- If it’s a duplicate, it won’t be resolved during the build forever.
- If I delete the ZEROGPU_V2 environment variable, I’m out of the build forever, but I can’t delete this guy.
- super_squash_history has no effect.
Are we swamped per something like the hardware number assigned to each VM?
I dare wait as I can’t delete ZEROGPU_V2=true, but if you are in a hurry and you don’t need environment variables, it seems to be faster to create a new space and migrate.