Traceback (most recent call last):
File "/home/user/app/app.py", line 399, in
demo.queue(max_size=16).launch(
File "/usr/local/lib/python3.10/site-packages/spaces/zero/gradio.py", line 142, in launch
task(*task_args, **task_kwargs)
File "/usr/local/lib/python3.10/site-packages/spaces/zero/torch/patching.py", line 348, in pack
_pack(Config.zerogpu_offload_dir)
File "/usr/local/lib/python3.10/site-packages/spaces/zero/torch/patching.py", line 340, in _pack
pack = pack_tensors(originals, fakes, offload_dir, callback=update)
File "/usr/local/lib/python3.10/site-packages/spaces/zero/torch/packing.py", line 114, in pack_tensors
os.posix_fallocate(fd, 0, total_asize)
OSError: [Errno 28] No space left on device

Please make the quota limit shared between interactive usage & api usage under a same account!

replied to victor's post about 2 months ago

Please provide more transparency to PRO account ZeroGPU quota limit.

My spaces run fine using the interface, but they won't run through API at all. Does that mean there are two different pools of quota for API & interface?

The error message was: The upstream Gradio app has raised an exception: You have exceeded your GPU quota (60s requested vs. 52s left). Create a free account to get more usage quota.

Even if I wait myself for a few days, the GPU quota available to me is still lower than 60s. Is there something wrong behind the stage?

For now, I am forced to convert all my Gradio API repo into the front end repo, which makes it gigantic and slow to rebuild and debug.