Mike

@benjaminhoffman My quick workaround for Lambda functions was to manually track the callbacks for every Segment call. I used a small class to help. This works OK for cloud function...

Yes. The only way to guarantee events are fully sent to Segment is to wait for the underlying HTTP request to complete. Network unreliability can cause this to take a...

@benjaminhoffman I just realized you stated you are "not using serverless functions." The solution I posted above was geared specifically for short-lived environments such as a cloud function invocation. In...

@emont01 I could see that. However, in this case It doesn’t matter as it is impossible for the promises to reject by design. The promises are resolved with an optional...

@emont01 Yes, I believe it is clear to everyone here that calling `process.exit()` immediately ends the Node process. Hence the need to await a full flesh before calling `process.exit()`. As...

No, my comment you linked to does not solve the stated issue. It is a hacky workaround for a fundamental flaw in key functionality of the library: the ability to...

> @yo1dog Sorry, I thought that your solution makes flushing deterministic. It does. It's workaround for part of the issue (deterministic flushing) but it is not a "solution" in that...

Unfortunately, I think "embarrassing" is the right word. **I recommend that no one use this library.** At least not directly. Just grab your favorite async batching library instead. Segment has...

Not sure if this is related, but this happens whenever I resize the window: 

same: just a few frames.