You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the chatbot streaming method that is showcased in the chatbot_streaming_main on HuggingFace, the submit (and the textarea field) are not disabled while the chatbot is streaming. For longer bot responses this is causing issues.
Immediately type another message and press enter before the bot is done completing it's message
The input box (and submit event) are not blocked while the bot is streaming and gives unexpected behaviour. This is likely because the "user" function has returned and then releases the disabled fields before it moves on to the "bot" function.
One solution would be to keep the disabled status during the "then" function, or otherwise make it possible to manually disable and enable fields in the gradio code.
Screenshot
No response
Logs
No errors are shown, it is resulting in unexpected UI behaviour.
System Info
Gradio==3.32.0
Severity
serious, but I can work around it
The text was updated successfully, but these errors were encountered:
Describe the bug
Following the chatbot streaming method that is showcased in the chatbot_streaming_main on HuggingFace, the submit (and the textarea field) are not disabled while the chatbot is streaming. For longer bot responses this is causing issues.
Is there an existing issue for this?
Reproduction
The input box (and submit event) are not blocked while the bot is streaming and gives unexpected behaviour. This is likely because the "user" function has returned and then releases the disabled fields before it moves on to the "bot" function.
msg.submit(user, [msg, chatbot], [msg, chatbot], queue=False).then( bot, chatbot, chatbot)
One solution would be to keep the disabled status during the "then" function, or otherwise make it possible to manually disable and enable fields in the gradio code.
Screenshot
No response
Logs
No errors are shown, it is resulting in unexpected UI behaviour.
System Info
Severity
serious, but I can work around it
The text was updated successfully, but these errors were encountered: