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
I think we have room for improvements on the exception handling side.
this is one example of output when a server side error happens:
HubspotServerError
Hubspot Error
---- request ----
POST api.hubapi.com/contacts/v1/contact/createOrUpdate/email/[email protected]?, [timeout=<class 'int'>]
---- body ----
<class 'NoneType'>
---- headers ----
<class 'dict'>
---- result ----
<class 'int'>
---- body -----
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>cloudflare</center>
</body>
</html>
---- headers -----
<class 'http.client.HTTPMessage'>
---- reason ----
Bad Gateway
---- trigger error ----
<class 'NoneType'>
As a solution on such cases we can catch the exception and try to somehow parse the reason, but would be way more convenient if such thing come from the package.
The text was updated successfully, but these errors were encountered:
I think we have room for improvements on the exception handling side.
this is one example of output when a server side error happens:
As a solution on such cases we can catch the exception and try to somehow parse the reason, but would be way more convenient if such thing come from the package.
The text was updated successfully, but these errors were encountered: