Nikita Koptelov

I like your solution more @delphinus. Pushing some value to the ctx and then rechecking it should do the trick.

Aha! Didn't know that the strategy's changed, thanks. I don't think there are any guards against running cancel on idle connections, but it won't save us from this race anyway:...

Yep, I guess it's an issue on their side :) thanks! I'll report that to upstream. ``` > go-chromecast ls error: unable to discover chromecast devices: unable to create new...

@gabe565 Yes, it does - I didn't do any rebuilds, so it seems like this issue happens with some specific OS setup.

Hmm, the more I look at it, the more I think they're isomorphic...

It might be related to this config: https://github.com/fedirz/faster-whisper-server/blob/master/src/faster_whisper_server/config.py#L244 Not sure why it's required - a long living websocket would be great to have, but then according to the settings, the...

just checked - keys of msteamscalling.deref().activeCallsService.activeCalls are the conversation/meeting IDs which can be used to get the participants. The keys need to be filtered (having calls.length() > 0). I've tried...

gotcha! so, first change is: ``` function getAppObjects() { if (typeof msteamscalling == "undefined") { return null; } let dref = msteamscalling.deref(); return { controller: dref, }; } ``` this...

I see there's a dictionary of those names somewhere in the minified code; there's loads of them 

``` bar.eventingService.asObservable.subscribe((e, data) => { console.dir(data); }); ``` - I see data.signalingSession.isIncomingCall in `data`! so assignIncomingCallCreatedHandler seems to be working now I can't find the event key yet though