Error: keepalive ping timeout; no close frame received about deepgram-python-sdk

[dvonthenen]

For this issue, the socket isn't receiving any data nor the keepalive message. That is expected behavior, but the SSL error is of concern. I don't have enough experience with the older version, so I will need to take some time to look at it.

PS: I re-opened this issue #183 in order to take a look at it, but not sure when I am going to get time as I have a bunch of things on my plate.

[ToxicityMax]

We recently migrated to v3 and implemented the flag options={"keepalive": "true"} in DeepgramClientOptions to maintain websocket connections. However, we're encountering the same persistent issue where, intermittently, the following error floods the logs, leading to a disruption in receiving transcripts:

This error seems to occur occasionally, but once it starts, it prevents us from receiving any further transcripts through that connection. Despite setting the keepalive flag, this issue persists.

It would be helpful if there are specific troubleshooting steps or additional configurations we should consider to mitigate this issue

[dvonthenen]

We recently migrated to v3 and implemented the flag options={"keepalive": "true"} in DeepgramClientOptions to maintain websocket connections. However, we're encountering the same persistent issue where, intermittently, the following error floods the logs, leading to a disruption in receiving transcripts:

Hi @ToxicityMax This reported issue is for v2 of the SDK. If you are having problems with v3, reach out to discuss in Discord or create a new issue. Before you do, please update to the latest v3.1.7 of the SDK.

[dvonthenen]

@SandraRodgers said she would take a look at this issue and the other one since she has more knowledge about the v2 client.