Eli Bishop

> And just to clarify, when using the in-memory store, variation always returns a Promise that is resolved in the very next tick, right? So it's not IO-bound ever? There's...

@crmitchelmore We'll update this issue as soon as there's anything to say. We've left the issue open because we haven't ruled it out, but we haven't committed to doing it...

This description is slightly unclear to me. I can't tell if you are asking for 1. the ability to send an arbitrary analytics event without having done an evaluation, or...

> This isn't that simple, we don't necessarily have the user ID at the place we consume the flag and we want to track it's consumption, therefore there could be...

This sounds like it could be a similar type of issue to https://github.com/launchdarkly/node-server-sdk/issues/233. Is there any chance that you are using a third-party package that modifies the behavior of `http.request`...

> I know libraries should have as minimal deps as possible but maybe pulling in axios or node-fetch to make these requests might help alleviate any request issues? I'm not...

It might be helpful if you could provide a list of your project's package dependencies.

> The reason I brought up those libraries is because if there is a disparate way they make requests to http-https they have probably already solved the issue If you...

I haven't ruled out the possibility that there is some other problem that might require a fix in `launchdarkly-eventsource`. But right now I have virtually nothing to go on, without...

@icarus-sullivan What issue did you mean to link to when you said "ticket 223"? There's no open issue with that number; GitHub has linked it to a pull request for...