-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Text To Speech Print statements in Python SDK - 1.40.0 #2610
Comments
This item has been open without activity for 19 days. Provide a comment on status and remove "update needed" label. |
Tried the latest this morning - 1.41.1. The prints(or log statements) are still there. Please change them over to debug, or silence them in some other way so we can upgrade. Thanks! |
Encountering the same issue with the speech to text recognizer, can't find any way to remove the logging statements |
Facing the same issue! |
After upgrading azure-cognitiveservices-speech to 1.40.0, in FastAPI python app I see PRINTS in the prod logs:
Info: on_underlying_io_bytes_received: Close frame received
Info: on_underlying_io_bytes_received: closing underlying io.
Info: on_underlying_io_close_complete: uws_state: 6.
Using text-to-speech on a python web app:
After downgrading back to azure-cognitiveservices-speech = "1.37.0"
the prints disappeared:
2024-10-01 08:27:28,744 - INFO - [text_to_speech_service_azure.py:78] - Synthesizing sentence: Good to hear everything's under control, Boyko.
2024-10-01 08:27:29,481 - INFO - [text_to_speech_service_azure.py:78] - Synthesizing sentence: As for me, I'm here and ready to chat as always.
2024-10-01 08:27:30,225 - INFO - [llm_service_abstract.py:77] - entire_llm_response: Good to hear everything's under control, Boyko. As for me, I'm here and ready to chat as always. What would you like to talk about today?
2024-10-01 08:27:30,227 - INFO - [text_to_speech_service_azure.py:78] - Synthesizing sentence: What would you like to talk about today?
Could you please remove the prints or switch them over to logging? Could you also add a linter that detects prints before you push the code as a package. Thanks!
The text was updated successfully, but these errors were encountered: