-
Notifications
You must be signed in to change notification settings - Fork 824
Pinned down websocket-client==1.1.0 #810
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
Comments
We at Home Assistant are having a similar issue. Pinned to |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This is still an issue |
This is still an issue: home-assistant/core#86336 |
@apaparazzi0329 could you please advise on this issue? It'd be great to have a solution for this fixed version. |
Still an issue for the same reason (homeassistant integration). As this seems to be noticed for almost 2 years now and regarding the presumably low effort for a fix this should be done soon. |
fixes watson-developer-cloud#810 and adds support for up to latest websocket-client (1.6.1)
fixes #810 and adds support for up to latest websocket-client (1.6.1)
Uh oh!
There was an error while loading. Please reload this page.
I work on a Speech Science software development team at CaptionCall. We have developed a system that can run audio through a selection of various speech-to-text ASRs --- including your
ibm-watson
recognizer. Apip
requirement for your recognizer iswebsocket-client==1.1.0
, pinned to one value. Other recognizers allow for a range of values which adds to the flexibility of our software system, enabling multiple recognizers to be selected during one run, without having to change software environments multiple times.Here's an example of one such conflict:
The text was updated successfully, but these errors were encountered: