Error

#3
by KSh100 - opened

Shows error when pressing submit

I just noticed it, and i get an error like:

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/gradio/queueing.py", line 532, in process_events
    response = await route_utils.call_process_api(
  File "/usr/local/lib/python3.10/site-packages/gradio/route_utils.py", line 276, in call_process_api
    output = await app.get_blocks().process_api(
  File "/usr/local/lib/python3.10/site-packages/gradio/blocks.py", line 1923, in process_api
    result = await self.call_function(
  File "/usr/local/lib/python3.10/site-packages/gradio/blocks.py", line 1509, in call_function
    prediction = await anyio.to_thread.run_sync(
  File "/usr/local/lib/python3.10/site-packages/anyio/to_thread.py", line 56, in run_sync
    return await get_async_backend().run_sync_in_worker_thread(
  File "/usr/local/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 2177, in run_sync_in_worker_thread
    return await future
  File "/usr/local/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 859, in run
    result = context.run(func, *args)
  File "/usr/local/lib/python3.10/site-packages/gradio/utils.py", line 832, in wrapper
    response = f(*args, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/spaces/zero/wrappers.py", line 144, in gradio_handler
    schedule_response = client.schedule(task_id=task_id, request=request, duration=duration)
  File "/usr/local/lib/python3.10/site-packages/spaces/zero/client.py", line 121, in schedule
    raise RuntimeError(f"ZeroGPU API /schedule error: {res} ({httpx.codes.get_reason_phrase(res)})") # pragma: no cover
RuntimeError: ZeroGPU API /schedule error: 500 (Internal Server Error)

Its a problem of ZeroGPU api, i think its having problems since some days, im going to see if factory rebuild can fix it or either i have to wait

Seems that the error has all been fixed, was a problem about ZeroGPU API, i will close this for now

Nick088 changed discussion status to closed

Sign up or log in to comment