Closed calvinl closed 3 years ago
Hello @calvinl ,
We're working on getting these specific error messages out ASAP.
Dante
@dantetam I upgraded from 1.5.3 to 1.5.4 over the weekend, and the Unknown errors seem to have gone away. It may have been related to #101?
@calvinl #112 should have fixed this. The problem was that our event sending logic was swallowing Node system errors without passing it on to client.
Hello,
I've filed this report with the support team, but they recommended opening a ticket here as well. I got word that the node SDK is swallowing some errors, so I wanted to create a ticket here to track it. I am willing to help out with a PR if necessary also.
We have this running on a system with Google pubsub, so we are retrying messages when we receive this error. Our messages backlog eventually goes down to 0, so they appear to succeed on retry, but it would be helpful to understand what this error is.
Expected Behavior
When pushing events to Amplitude via
client.logEvent()
, it should return a meaningful error message.Current Behavior
We are receiving a lot of errors like the following:
Possible Solution
Unsure
Steps to Reproduce
Environment