Switched from AsyncDuplicateLock to AsyncKeyedLock#191
Switched from AsyncDuplicateLock to AsyncKeyedLock#191MarkCiliaVincenti wants to merge 52 commits intoopenactive:masterfrom
Conversation
|
@nickevansuk nudge :) |
|
Thanks for this @MarkCiliaVincenti, very helpful - note that it has previously failed in CI for .NET Framework. Have approved a new run so fingers crossed this time it passes... otherwise it probably just needs a dependency update in the .NET Framework project. |
Does it usually take this long? |
|
OK, made some changes, try again now @nickevansuk? |
|
@nickevansuk framework ones are failing halfway through. I see it's been a long time since these tests have passed. I'm not convinced the changes I made have broken anything. What are your thoughts? |
|
It looks like there's some issue with .NET Framework that requires some investigation on our side? Is that right? If so have added it to the backlog |
There must be. I guess that's a prerequisite for this getting merged? |
|
Afraid so - we can't release something that fails CI |
|
@nickevansuk any luck so far? |
|
Nothing yet - hoping to get some time to look in the next couple of weeks. It's a deep issue so needs some proper investigation. |
OK, I updated to 6.2.0 meanwhile although there are no changes that affect you unless you would consider using the new striped locking technique instead. |
|
@nickevansuk any luck yet? |
|
@nickevansuk do you intend on fixing the persistent issue or shall I close the PR? |
|
Can you please try now @nickevansuk ? |
|
Shall we close this @nickevansuk ? |
Switched from AsyncDuplicateLock to AsyncKeyedLock, which provides better performance and lower memory usage.