-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
The examples run only once, then they begin to generate error #1809
Comments
Hi @kmkarakaya, I can't seem to reproduce the issue in your Space. Did you figure it out? |
Hi @abidlabs, NO. I just set cache_examples = False to avoid the issue. Now I removed the "cache_examples = False" parameter. If you re-try the examples few times you can experience the issue. Regards |
Hmm yes I see the issue, thanks we'll take a look at it. |
I'm having the same issue with a huggingface space |
@dhansmair @kmkarakaya this should be fixed now! We'll release a new version of |
Should be fixed in |
Unfortunately, even I set up gradio==3.1.1 in the requirements.txt, the ERROR msg still appears. |
Hi @kmkarakaya ! Can you post the logs? Might help us figure out what's happening. |
Ah I think I know the issue. Setting the version in requirements.txt doesn't work on Spaces. You have to set the |
@abidlabs yes, this time it works smoothly. Thank you for your consideration and help. |
Describe the bug
When I deploy an app on Spaces, the examples run only once, then if I click one of them they begin to generate error.
After building an app on spaces, each example run perfectly ONLY for ONCE. When I click any of them for the second or more times on the screen I only see ERROR message.
However, I can enter a new prompt manually and it works fine.
If I re-build the app, again the examples run only ONCE.
I checked the log but there seems no problem.
As far as I understood, there is a problem to fetch the cached example and its result.
Thank you in advanced
Is there an existing issue for this?
Reproduction
kmkarakaya/Auto_Review_Generation_in_Turkish
Screenshot
Logs
System Info
Severity
serious, but I can work around it
The text was updated successfully, but these errors were encountered: