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
When running the module locally, I get the following error: ERROR in Sentry Plugin: RequestError: Error: getaddrinfo ENOTFOUND sentry.io sentry.io:443
After a bit of search, it looks like the request-promise module sometimes fails randomly on the DNS lookup using the Node native API.
I tried passing the family: 4 option in the requests of the local node_modules version of this plugin as described in the linked issue above with no luck. Clearing my DNS cache didn't do the work either.
Did anyone else also encounter this issue?
One solution might be to use another library like axios to perform the requests to the Sentry API.
After further investigation, it turns out that this error happens because our app uses the webpack 4 AggressiveSplittingPlugin which ends up generating more than 450 files, including sourcemaps.
Since the plugin currently launches all the requests in parallel, most of them fail, probably because of a dns or sockets saturation.
I'm going to open a PR to throttle launching the request using es6-promise-pool that I was able to test successfully on our project.
Hi,
When running the module locally, I get the following error:
ERROR in Sentry Plugin: RequestError: Error: getaddrinfo ENOTFOUND sentry.io sentry.io:443
After a bit of search, it looks like the
request-promise
module sometimes fails randomly on the DNS lookup using the Node native API.I tried passing the
family: 4
option in the requests of the localnode_modules
version of this plugin as described in the linked issue above with no luck. Clearing my DNS cache didn't do the work either.Did anyone else also encounter this issue?
One solution might be to use another library like
axios
to perform the requests to the Sentry API.My current configuration is:
[email protected]
[email protected]
[email protected]
[email protected]
The text was updated successfully, but these errors were encountered: