Open FurkanGozukara opened 1 year ago
Hi @FurkanGozukara I faced the same issue while running Gradio project in docker container. Have you resolved this issue?
Hi @FurkanGozukara I faced the same issue while running Gradio project in docker container. Have you resolved this issue?
nope i couldn't. only share option working
@FurkanGozukara @JindaHuang We may have a fix for you here: https://github.com/gradio-app/gradio/pull/6556
Could you try installing gradio from this branch? You can do it by doing:
pip install https://gradio-builds.s3.amazonaws.com/756e3431d65172df986a7e335dce8136206a293a/gradio-4.7.1-py3-none-any.whl
@FurkanGozukara @JindaHuang We may have a fix for you here: #6556
Could you try installing gradio from this branch? You can do it by doing:
pip install https://gradio-builds.s3.amazonaws.com/756e3431d65172df986a7e335dce8136206a293a/gradio-4.7.1-py3-none-any.whl
sorry for delay i just tested
it works but interface update speed is very slow
Ok I've renamed the issue, we'll take a look into this when we get a chance. If there are any other details you can provide about why it might be slow, that would be helpful!
Ok I've renamed the issue, we'll take a look into this when we get a chance. If there are any other details you can provide about why it might be slow, that would be helpful!
I noticed slowness from update frequency of the step progress %. Normally it updates % of steps after each step but it was like 5 6x slower. So instead of like every second it was like once 5 6 seconds I don't know sadly why could be.
Hi @FurkanGozukara can you please check if the latest version of gradio
(4.21) still has this issue? We made some fixes to how Gradio works behind proxies which may have solved this issue
Hi @FurkanGozukara can you please check if the latest version of
gradio
(4.21) still has this issue? We made some fixes to how Gradio works behind proxies which may have solved this issue
it works but i got this error like after 100 seconds of working any ideas?
I made it even like this and still didnt fix
if args.port is not None: # Check if the --port argument is provided
block.queue().launch(server_name=server_ip, server_port=args.port, share=args.share, inbrowser=True)
else:
block.queue().launch(server_name=server_ip, share=args.share, inbrowser=True)
The app works perfectly fine. The gradio timesout
524 is a Cloudflare specific timeout I think. Weird.
524 is a Cloudflare specific timeout I think. Weird.
Gradio live share working
In past I had this error and queue() was solving but this time didnt
@FurkanGozukara could you see if this happens with any Gradio app with a long running predict function? A simple repro would be helpful here as we look into it
@FurkanGozukara could you see if this happens with any Gradio app with a long running predict function? A simple repro would be helpful here as we look into it
i can start a machine and give you gradio live share link and runpod proxy link when is a good time?
Hi @FurkanGozukara, apologies for the late follow up. We haven't had a chance to look into this issue, but the Gradio codebase has changed quite significantly since this issue was created, particularly with the release of Gradio 5. Could you let us know if this is still an issue in the latest version of Gradio (pip install --upgrade gradio
)? Thanks!
Describe the bug
I am running gradio 4.7.1 and using this web app : https://github.com/PixArt-alpha/PixArt-alpha/blob/master/scripts/app.py
When using Gradio share or running locally it is working great
When I use
The gradio starts but when I do inference this is the error
Severity
Blocking usage of gradio
Example working on local