Sam Cook

I just made a simple test console app (.NET Core 2.1) referencing RedLock.net 2.2.0 and Microsoft.Extensions.Logging 3.0.0-preview9.19423.4 - it seems to work fine.

Thanks for the quick reply. Re the `--agents` parameter, we do test multiple assemblies in our TC build so it's applicable there, I'd narrowed it down to a single assembly...

Yes, we're referencing the latest framework version (3.12). I've also tried building the latest master version of the framework and debugging with that, and I'm able to reproduce it there...

So, further digging... This is probably why that thread disappears.  When I stepped on from that I was in `Reflect.cs` (https://github.com/nunit/nunit/blob/d8490ecd6171538fa0ba9cb5d38948bde5ebd61e/src/NUnitFramework/framework/Internal/Reflect.cs#L270) with a `TargetInvocationException`, but on the next step...

In these situations, is the lock continuing to renew itself due to execution still being inside your code within the redlock `using` block? Or do you think that execution has...

> And that's quite critical because it is not an IDisposable we get as the result of the using (when using CreateAsync), but instead an IAsyncDisposable. That's not quite true....

Both `CreateLock` and `CreateLockAsync` return an instance of `IRedLock` (see [here](https://github.com/samcook/RedLock.net/blob/master/RedLockNet.Abstractions/IDistributedLockFactory.cs)). And `IRedLock` is both `IDisposable` and `IAsyncDisposable` (see [here](https://github.com/samcook/RedLock.net/blob/master/RedLockNet.Abstractions/IRedLock.cs#L5)). The creation of the lock object and the disposal of...

Hi @Tasteful, I've had a look and managed to reproduce the issue - it seems like there's an issue with StackExchange.Redis when it loses its current sentinel connection (and your...

I haven't tried using it with .NET 7, but it should work (and if it doesn't for some reason then I'd like to fix it)

So I've just run the unit tests locally targeting `net7.0` and they all passed. Are you able to provide a repro for this failure, or enable the RedLock logging and...