Gutemberg Ribeiro

Ok, now I understand :) The `IXXXXTelemetryConsumer` are the ingest entrypoint for telemetry. The implementation of those consumers can write its own sink, or just directly push to the underlying...

> TrackCounter, IncrementCounter, DecrementCounter - for long integers > TrackTimeSpanMetric, IncrementTimeSpanMetric, DecrementTimeSpanMetric Let me get to the telemetry API again and I'll hit you again with it.

@danvanderboom that is what I'm trying to say... Its a judgement call that a custom telemetry consumer must do when you are implementing it. I don't think your extension should...

No problem. For some reason the service container for the emulator doesn't seems to be running on some of the test jobs. I've ran it against a real Cosmos Account...

Feedback addressed @ReubenBond. Sorry for taking so long.

There shouldn't be any differences or special config. They all pass on my machine either on the emulator or targeting a real account @benjaminpetit. I'll pull your changes in and...

It seems like there is something with the setup on GH for the tests, will look at it. It run fine on the local emulator (tried on a windows VM...

Right before we start to see that original hanging message, I start to see `PubSubRendezvousGrain` being deactivated. They start to appear a lot more of those messages up to a...

I can't find the cause but, it is hanging on those two spots: https://github.com/OrleansContrib/SignalR.Orleans/blob/master/src/SignalR.Orleans/Core/ConnectionGrain.cs#L68 https://github.com/OrleansContrib/SignalR.Orleans/blob/master/src/SignalR.Orleans/Clients/ClientGrain.cs#L111 In both cases it seems the calls to `PubSubRendezvousGrain.UnregisterConsumer(GuidId subscriptionId, StreamId streamId)` pile up over...

More updates. After debugging the memory dumps from when the problem happened with @ReubenBond we've found where the deadlock is. For a bit of context, whenever a SignalR client connects...