Fix - Under load and during topology changes, thread saturation can occur, causing a lockup #2503
Annotations
11 warnings
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Run tests tests/Proto.Cluster.PartitionIdentity.Tests/*.csproj
'Log.CreateLogger<T>()' is obsolete: 'Inject ILogger<T> instead'
|
Run tests tests/Proto.Cluster.PartitionIdentity.Tests/*.csproj
'Log.CreateLogger<T>()' is obsolete: 'Inject ILogger<T> instead'
|
Run tests tests/Proto.Cluster.PartitionIdentity.Tests/*.csproj
The variable 'x' is declared but never used
|
Run tests tests/Proto.Cluster.PartitionIdentity.Tests/*.csproj
'Log.CreateLogger<T>()' is obsolete: 'Inject ILogger<T> instead'
|
Run tests tests/Proto.Cluster.PartitionIdentity.Tests/*.csproj
'Log.CreateLogger<T>()' is obsolete: 'Inject ILogger<T> instead'
|
Run tests tests/Proto.Cluster.PartitionIdentity.Tests/*.csproj
'Log.CreateLogger<T>()' is obsolete: 'Inject ILogger<T> instead'
|
Run tests tests/Proto.Cluster.PartitionIdentity.Tests/*.csproj
'Log.CreateLogger<T>()' is obsolete: 'Inject ILogger<T> instead'
|
Run tests tests/Proto.Cluster.PartitionIdentity.Tests/*.csproj
'Log.CreateLogger<T>()' is obsolete: 'Inject ILogger<T> instead'
|
Run tests tests/Proto.Cluster.PartitionIdentity.Tests/*.csproj
'Log.CreateLogger<T>()' is obsolete: 'Inject ILogger<T> instead'
|
Run tests tests/Proto.Cluster.PartitionIdentity.Tests/*.csproj
'Log.CreateLogger<T>()' is obsolete: 'Inject ILogger<T> instead'
|
Loading