Patric Forsgard

I don't remember why I was setting it to `null` in the first case, but when I upgraded the OpenAPI package it was a change in the behavior that was...

Nice, i will try to use that one. I can say directly that I got no errors :)

Maybe if the `RefAssemblyPaths="@(_ResolveAssemblyReferenceResolvedFiles)"` on the task is changed to a private variable we probably can filter out the netstandard2.0 reference from that one and the IDT001 warning can still...

+1 Why not 'simpleClassAndMethod' that will ignore all namespace parts that are same for all test cases?

@NickCraver no. That route is not so extensible that a format settings. If we look at the aspnet dev guidelines https://github.com/aspnet/Home/wiki/Engineering-guidelines#unit-test-class-naming the test-class should live in the same namespace as...

@NickCraver We have identified something similar with this, see https://github.com/samcook/RedLock.net/issues/112#issuecomment-2187152737 It exists cases when sentinel returns IP addresses that isn't longer included in the cluster, the connection multiplexer will work...

> @Tasteful please correct my assumptions if they are wrong. This issue is likely to be encountered by anyone calling `IConnectionMultiplexer.GetServer(...)` while using Redis Sentinel running in Kubernetes. The only...

@NickCraver Did you have time to check the above question about GetEndpoints/GetServer? @mgravell maybe you have insigth into this area as well.

We are getting the same issue in one of our production environment and I have been able to track down the reason. First, we are using redis sentinel with an...

@samcook Do you have time to look into this and the linked PR? Maybe a patch release with this? Our workaround with using host names instead of IPs did not...