fix title #323
Annotations
11 warnings
|
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Build:
AsyncKeyedLock.Tests/AsyncKeyedLocker/OriginalTests.cs#L231
Dereference of a possibly null reference.
|
|
Build:
AsyncKeyedLock.Tests/AsyncKeyedLocker/OriginalTests.cs#L244
Dereference of a possibly null reference.
|
|
Build:
AsyncKeyedLock.Tests/AsyncNonKeyedLockerTests/OriginalTests.cs#L299
'AsyncNonKeyedLocker.Lock(int, out bool)' is obsolete: 'Use LockOrNull method instead as it is more performant.'
|
|
Build:
AsyncKeyedLock.Tests/AsyncNonKeyedLockerTests/OriginalTests.cs#L304
'AsyncNonKeyedLocker.Lock(int, out bool)' is obsolete: 'Use LockOrNull method instead as it is more performant.'
|
|
Build:
AsyncKeyedLock.Tests/StripedAsyncKeyedLocker/OriginalTests.cs#L362
'StripedAsyncKeyedLocker<string>.LockAsync(string, int, bool)' is obsolete: 'Use LockOrNullAsync method instead as it is more performant.'
|
|
Build:
AsyncKeyedLock.Tests/AsyncNonKeyedLockerTests/OriginalTests.cs#L336
'AsyncNonKeyedLocker.Lock(TimeSpan, out bool)' is obsolete: 'Use LockOrNull method instead as it is more performant.'
|
|
Build:
AsyncKeyedLock.Tests/AsyncNonKeyedLockerTests/OriginalTests.cs#L341
'AsyncNonKeyedLocker.Lock(TimeSpan, out bool)' is obsolete: 'Use LockOrNull method instead as it is more performant.'
|
|
Build:
AsyncKeyedLock.Tests/StripedAsyncKeyedLocker/OriginalTests.cs#L386
'StripedAsyncKeyedLocker<string>.Lock(string, int, out bool)' is obsolete: 'Use LockOrNull method instead as it is more performant.'
|
|
Build:
AsyncKeyedLock.Tests/StripedAsyncKeyedLocker/OriginalTests.cs#L390
'StripedAsyncKeyedLocker<string>.Lock(string, int, out bool)' is obsolete: 'Use LockOrNull method instead as it is more performant.'
|
|
Build:
AsyncKeyedLock.Tests/StripedAsyncKeyedLocker/OriginalTests.cs#L392
'StripedAsyncKeyedLocker<string>.Lock(string, TimeSpan, out bool)' is obsolete: 'Use LockOrNull method instead as it is more performant.'
|
Loading