Alex Gustafsson

The workaround I've used is simply disabling the builtin log package as I use another package. ```go // Not ideal, but the ffmpeg library uses log.Printf to print the "compiled"...

At first, that didn't seem to work for me. Digging a bit deeper, it seems as if this might have been the culprit: https://github.com/microsoft/ApplicationInsights-node.js/blob/c060888eb97d6a8d55366ebbfc49243f4f2794c4/Library/Config.ts#L118 And in turn, this part of...

I tried to log the `telemetryClient.config.correlationId` right after having created it and then at the end of the test - and sure enough, it's empty ("cid-v1:") at first, but set...

Yes, that seems as exactly what's going on here. Waiting for some seconds does let the `CorrelationIdManager` complete, thus closing the handle.

That sounds like a great solution for my use case at least.

@mohsha-msft Is it still planned for release in March?

@mohsha-msft Hi! Is there any timeline on when this will be fixed?

803613664

Thank you for taking the time. Yes, they are expected - I'll look into fixing the auth issues. When it comes to the error I get, why would I see...

Weird! No change on our end and I assume no change on your end, right?