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
The elements (Upload, Record, Realtime speech) should keep disabled until all initialization work finishes, but I found that the elements remove the disabled attribute and become clickable when processor_config fails to download.
The text was updated successfully, but these errors were encountered:
Thanks @NingW101. In the original design, it will access second URL if the first one fails (the first try was for local deployment scenario), so the first 404 should be OK, and we can get HTTP 200 for the second preprocessor_config.json. Do you mean you cannot download preprocessor_config.json anyway?
In the original design, it will access second URL if the first one fails (the first try was for local deployment scenario), so the first 404 should be OK, and we can get HTTP 200 for the second preprocessor_config.json.
Exactly. It will try to fetch the second configuration json file from huggingface and everything goes well if the network is good.
I encountered this issue because of my local network and found that the elements were clickable even the bug occurred.
The elements (
Upload, Record, Realtime speech
) should keep disabled until all initialization work finishes, but I found that the elements remove thedisabled
attribute and become clickable whenprocessor_config
fails to download.The text was updated successfully, but these errors were encountered: