Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: connect ETIMEDOUT 34.96.125.79:443 #204

Open
galaxyfeeder opened this issue Sep 20, 2022 · 0 comments
Open

Error: connect ETIMEDOUT 34.96.125.79:443 #204

galaxyfeeder opened this issue Sep 20, 2022 · 0 comments

Comments

@galaxyfeeder
Copy link

Our system is capturing from time to time, once a month more or less, the following error that seems that is not handled by the SDK.

Error: connect ETIMEDOUT 34.96.125.79:443
    at __node_internal_captureLargerStackTrace (node:internal/errors:477:5)
    at __node_internal_exceptionWithHostPort (node:internal/errors:655:12)
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1247:16) 

That IP address is the IP address of mixpanel eu API as can be seen in the DNS records for api-eu.mixpanel.com.

In our code we are promisifying mixpanel.track and capturing the errors sent to the callback, however, fmpov this should have been handled by the SDK and been retried by the SDK.

At the end, has that event been sent, we guess that isn't sent.

  • Is this the expected behaviour?
  • Does the SDK handle any error by itself?-
  • Should all errors be handled by the integrator?
  • What other errors can be thrown by the SDK?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant