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
{{ message }}
Repository navigation
sift.client.ApiException: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer')) #82
We're seeing some 104 Connection Reset errors from the v205 Events POST endpoint. We're using version 5.0.1 of the SDK. It looks like this is an issue with the underlying calls to requests. Is this a known issue? What's the best way to handle these exceptions?
Hello!
I have the same problem, we are using asynchronous microservices where we are tracking events with Sift sdk with python language, I am controlling the problem with a retry when it fails but the error rate is very high. It looks like the sift sdk is not 'ready' and keeps crashing when still being used... the error trace is coming from the sift sdk connection layer
Hi there, is there any update on this one? 🙏🏾 Are there any recommendations on how to handle this until it's fixed? Should we be retrying API calls if we get this error?
@ashwinv11 we are working on getting this work scheduled. Our current suggestion is to retry these requests when you get these exceptions. Thanks for your patience.
Please, provide a code snippet of how they init a Sift client in the Python code (without credentials)
Do you create a session object manually, or use the Sift's default one? If you create Session by your own please provide a code snippet or parameters. Also, do you use own timeout or rely on the Sift's default one (2 sec)?
Python version – 3.9.16
Requests lib version – 2.25.1
Here's an example of how we have it setup. Looks like we set a longer timeout than the default, and don't build the session object manually. We don't use any proxy when calling Sift.
@ashwinv11 Could you pls try to add some pre-configuration before creating a Sift Client using the code snipped below? Basically, it will configure the Session object particularly and only for the Sift Client, and only requests to the Sift API will be affected by that.
Activity
vincent-sift commentedon Apr 26, 2022
Hello @ashwinv11 thanks for letting use know.
Thanks :)
StevenLudwig commentedon May 18, 2022
Hello!
I have the same problem, we are using asynchronous microservices where we are tracking events with Sift sdk with python language, I am controlling the problem with a retry when it fails but the error rate is very high. It looks like the sift sdk is not 'ready' and keeps crashing when still being used... the error trace is coming from the sift sdk connection layer
vincent-sift commentedon May 19, 2022
Thanks @StevenLudwig we are investigating this issue.
ashwinv11 commentedon Jun 8, 2022
Hi @vincent-sift just reached out to support with some additional information. Thanks!
vincent-sift commentedon Jun 8, 2022
Thanks @ashwinv11. I am following up with the engineering team as well.
ashwinv11 commentedon Jul 7, 2022
Hi there, is there any update on this one? 🙏🏾 Are there any recommendations on how to handle this until it's fixed? Should we be retrying API calls if we get this error?
vincent-sift commentedon Jul 20, 2022
@ashwinv11 we are working on getting this work scheduled. Our current suggestion is to retry these requests when you get these exceptions. Thanks for your patience.
ashwinv11 commentedon Nov 11, 2022
Hey @vincent-sift any update on this?
viaskal-sift commentedon Jun 2, 2023
@ashwinv11 a few questions:
sessionobject manually, or use the Sift's default one? If you create Session by your own please provide a code snippet or parameters. Also, do you use owntimeoutor rely on the Sift's default one (2 sec)?requestslib?Thanks!
ashwinv11 commentedon Jun 2, 2023
Hey @viaskal-sift sure!
Python version –
3.9.16Requests lib version –
2.25.1Here's an example of how we have it setup. Looks like we set a longer timeout than the default, and don't build the
sessionobject manually. We don't use any proxy when calling Sift.Hope this helps!
viaskal-sift commentedon Jun 23, 2023
@ashwinv11 Could you pls try to add some pre-configuration before creating a Sift Client using the code snipped below? Basically, it will configure the Session object particularly and only for the Sift Client, and only requests to the Sift API will be affected by that.
viaskal-sift commentedon Jul 10, 2023
@ashwinv11 did you have a chance to try this one? Thanks!
stephenflynn commentedon Jul 12, 2023
Hi Viaskal, we're hoping to tackle this guy soon.
viaskal-sift commentedon Aug 1, 2023
@stephenflynn any updates from your side?
jmdsifty commentedon Oct 4, 2023
Hi @stephenflynn wanted to check if @viaskal-sift 's recommendation was able to resolve the issue? Thank you!