Keepalive thread throws errors even when the "keepalive" option is not set about deepgram-python-sdk

[roerohan]

Thanks! I'll take a look at it after some time.

Also, I noticed a minor mistake in the logs, so I created a PR #347

[roerohan]

Also, in v3.2.1, there's no way for me to handle exceptions raised by the send method, because they're caught within the SDK and logged, as you can see here

deepgram-python-sdk/deepgram/clients/live/v1/async_client.py

Lines 358 to 361 in 2d0ddf1

	except websockets.exceptions.WebSocketException as e:
	self.logger.error("send() failed - WebSocketException: %s", str(e))
	self.logger.spam("AsyncLiveClient.send LEAVE")
	return False

Now, let's say I want to reconnect if there's an exception in self._socket.send, there's no way for me to do it using the SDK, other than using self._socket.send directly instead of AsyncLiveClient.send, which beats the purpose of the class.

[dvonthenen]

Ooops. That's definitely a bug after the refactor. We should not be kicking off the thread off if the keepalive isn't enabled. Will also toggle post an error on the callback which is missing and provide a switch to handle the exception yourself.

Will have that fixed this morning.

[dvonthenen]

hi @roerohan

This should address your issue:
https://github.com/deepgram/deepgram-python-sdk/releases/tag/v3.2.2

If you want to enable passing the exceptions up, there are options to do that now on top of fixing the keepalive issue. If you have any problems with this, catch me in discord for real-time help.

[dvonthenen]

Here are some examples to demonstrate expected failures when not using and also how to utilize the feature correctlyhttps://github.com//pull/348