-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no output #34
Comments
这个问题你最后有解决吗,我也遇到相同的问题 |
不,我也想要这个项目。 您是否有使用张量流模型的电子商务网站项目虚拟更衣室? |
Same problem here, the output is empty |
i had run the application using colab it ran perfectly fine |
I want this code run in my local machine.
…On Wed, 25 Dec 2024 at 11:48, Sumit Sah ***@***.***> wrote:
i had run the application using colab it ran perfectly fine
—
Reply to this email directly, view it on GitHub
<#34 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BHP75IMPLRFXJDDEOZHLXWL2HJEZ3AVCNFSM6AAAAABQNKPPQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRRGY2DOMZRHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I tried running it using colab and uploaded sample images in the gradio app - it did not show any output not sure why |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/gradio/routes.py", line 517, in predict
output = await route_utils.call_process_api(
File "/usr/local/lib/python3.10/dist-packages/gradio/route_utils.py", line 216, in call_process_api
output = await app.get_blocks().process_api(
File "/usr/local/lib/python3.10/dist-packages/gradio/blocks.py", line 1555, in process_api
result = await self.call_function(
File "/usr/local/lib/python3.10/dist-packages/gradio/blocks.py", line 1193, in call_function
prediction = await anyio.to_thread.run_sync(
File "/usr/local/lib/python3.10/dist-packages/anyio/to_thread.py", line 33, in run_sync
return await get_asynclib().run_sync_in_worker_thread(no execution
The text was updated successfully, but these errors were encountered: