You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if a channel has gone away and we attempt to send an action for that channel it'll throw a requests.exceptions.HTTPError (404).
That's fine and I understand why that is thrown. However, it would be nice to have the ari client catch the raw HTTPErrors and have its own exceptions (ari.exceptions).
This way, when using the client, we can catch exceptions like ari.exceptions.ChannelNotFoundException or however you want to name it and not have to catch the underlying requests.exceptions.
Ryan
The text was updated successfully, but these errors were encountered:
Hey,
Currently, if a channel has gone away and we attempt to send an action for that channel it'll throw a requests.exceptions.HTTPError (404).
That's fine and I understand why that is thrown. However, it would be nice to have the ari client catch the raw HTTPErrors and have its own exceptions (ari.exceptions).
This way, when using the client, we can catch exceptions like ari.exceptions.ChannelNotFoundException or however you want to name it and not have to catch the underlying requests.exceptions.
Ryan
The text was updated successfully, but these errors were encountered: