Azure / Azure/azure-sdk-for-python
azure-ai-voicelive: unhandled websocket message type CLOSING results in error
- Vorherrschende Sprache
- Python
- Sterne
- 5.6k
- Forks
- 3.4k
- Ø Merge
- 2 T. 2 Std.
- Gemergte PRs (30 T.)
- 213
Beschreibung
- **Package Name**: azure-ai-voicelive
- **Package Version**: 1.1.0
- **Operating System**: linux
- **Python Version**: 3.12
**Describe the bug**
When integrated in a websocket, voicelive SDK has no logic to manage `CLOSING` as received websocket message type, only `CLOSE` and `CLOSED`. Other Azure service return closing, resulting in websocket errors. `CLOSING` is fairly common so I believe it should be included, specially since this service is made to be integrated in a websocket with others. You can find the relevant code here: https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/voicelive/azure-ai-voicelive/azure/ai/voicelive/aio/_patch.py#L523
**To Reproduce**
Steps to reproduce the behavior:
1. Create the websocket
2. Make the other party return CLOSING
3. Results in error
**Expected behavior**
CLOSING message type should not error out. Either needs to be handled or ignored.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Additional context**
Our session id was: **sess_6Zxvf6tkDngFpn3CwcvbTE**
Please do not hesitate to reach out for more data points. Thank you.
Beitragsleitfaden
Rechercherichtung
Beginne in sdk/voicelive/azure-ai-voicelive/azure/ai/voicelive/aio/_patch.py bei der Behandlung von websocket-Nachrichten um Zeile 523. Reproduziere nach Möglichkeit eine CLOSING-Nachricht und verfolge, wie CLOSE und CLOSED behandelt werden. Als abgeschlossen gilt die Aufgabe, wenn CLOSING behandelt oder ignoriert wird, ohne einen websocket-Fehler zu erzeugen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- python
- Bereich
- api
- Issue-Typ
- Bug
- Schwierigkeit
- 2/5
- Geschätzter Aufwand
- 1-3 Stunden
- Aktivitätsstatus
- Veraltet
- Klarheit
- Klar beschrieben
- Anfängerfreundlichkeit
- 68/100