Tyler Ohlsen

This issue is now being tracked here: [dotnet/coreclr/issue#26344](https://github.com/dotnet/coreclr/issues/26344). But also know that the issue is *not* present in .Net Core 3.0 which is currently supported in production environments and will...

I just ran into the same issue. AWS ElastiCache with 3 nodes had a failover of the primary from node 1 to node 3. It seems that our services continue...

@NickCraver I already have the fix from #2012. This is similar, I imagine there must be another code path that's trying to run another CLUSTER command that isn't protected by...

@mgravell I'm using a Redis cluster as a SignalR backplane and using it for PubSub only. Each node of the cluster is physically separated by a large distance. I have...

@NickCraver I thought that version stamp was incorrect because I thought I was using a MyGet pre-release version of the library. I see now that you are correct and that...

Yep, all good. Thanks

> all we can do is mark the incomplete task as complete (with cancellation) That would allow the client application flow to continue, which is what is important to me...

All of the existing implementation should not be affected, so I don't think a major rev is necessary. But probably a minor rev.

Overloads got a bit more palatable with expression bodied function members. ```c# public Task StringGetAsync(RedisKey key, CommandFlags flags = CommandFlags.None) => StringGetAsync(key, CancellationToken.None, flags); public Task StringGetAsync(RedisKey key, CancellationToken token,...

Another option would be that `WithCancellation(token)` could set the token in an internal AsyncLocal ambient context. Then the method signatures would not need to change at all.