add status tracker to md and html#2474
Conversation
|
All the demos for this PR have been deployed at https://huggingface.co/spaces/gradio-pr-deploys/pr-2474-all-demos |
|
Looks like this closes at #1985 as well (I'll update the main block to reflect that) |
|
I'll let you in on a secret. When i created that other issue i ticked this:
But i didn't search the existing issues at all. |
freddyaboulton
left a comment
There was a problem hiding this comment.
Thanks @pngwn ! Tested out locally and it works!
|
Thanks so much for working on this @pngwn! Any idea when this change will get deployed on spaces? |
|
Hi @ola13 most likely this should be out tomorrow in gradio 3.5.1 (you’ll have to upgrade the version of gradio if you have an existing Space) |
|
Hi @abidlabs a quick question - how can I upgrade the version manually? Should I create a requirements file with the specified version? I rebooted my app and it seems it's installing gradio 3.1.3: |
|
Hello another question, cc @pngwn :) So I'm experimenting with the feature and it works great the first time I load the HTML - however, when I update inputs and re-issue a query, I no longer get a status tracker - you can test it here: https://4fce965b9b0a2363.gradio.app/ - try querying and then requerying - the results are stored in the |
|
Yeah, this is a bug, will take a look. |
|
@ola13 with regards to your question, you will need to update the |
|
Thanks @abidlabs! |
Description
Adds status tracker to Markdown and HTML components in order to give end users feedback that the a response is pending.
Closes #2473.
Closes #1985
Can be tested with the following snippet:
Please include:
Closes: # (issue)
Checklist:
A note about the CHANGELOG
Hello 👋 and thank you for contributing to Gradio!
All pull requests must update the change log located in CHANGELOG.md, unless the pull request is labeled with the "no-changelog-update" label.
Please add a brief summary of the change to the Upcoming Release > Full Changelog section of the CHANGELOG.md file and include
a link to the PR (formatted in markdown) and a link to your github profile (if you like). For example, "* Added a cool new feature by
[@myusername](link-to-your-github-profile)in[PR 11111](https://github.com/gradio-app/gradio/pull/11111)".If you would like to elaborate on your change further, feel free to include a longer explanation in the other sections.
If you would like an image/gif/video showcasing your feature, it may be best to edit the CHANGELOG file using the
GitHub web UI since that lets you upload files directly via drag-and-drop.