updated unit test settings #424
Annotations
22 warnings
|
Build Samples:
src/SuperSocket.Connection/Sockets/SocketSender.cs#L17
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build Samples:
src/SuperSocket.Connection/Sockets/SocketSender.cs#L17
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Test - Windows:
src/SuperSocket.Connection/Sockets/SocketSender.cs#L17
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Test - Windows:
test/SuperSocket.Tests/AspNetIntegrationTest.cs#L96
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Test - Windows:
test/SuperSocket.Tests/AspNetIntegrationTest.cs#L106
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Test - Windows:
test/SuperSocket.Tests/AspNetIntegrationTest.cs#L140
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Test - Windows:
test/SuperSocket.Tests/AspNetIntegrationTest.cs#L150
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Test - Windows:
test/SuperSocket.Tests/AspNetIntegrationTest.cs#L212
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Test - Windows:
test/SuperSocket.Tests/AspNetIntegrationTest.cs#L218
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Test - Windows:
test/SuperSocket.Tests/AspNetIntegrationTest.cs#L219
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Test - Windows:
test/SuperSocket.Tests/AspNetIntegrationTest.cs#L228
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Test - Windows:
test/SuperSocket.Tests/WebSocket/WebSocketBasicTest.cs#L155
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Build
The target framework 'net7.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
|
|
Build
The target framework 'net7.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
|
|
Build:
src/SuperSocket.Connection/Sockets/SocketSender.cs#L17
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
src/SuperSocket.Connection/Sockets/SocketSender.cs#L17
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
src/SuperSocket.Connection/Sockets/SocketSender.cs#L17
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
test/SuperSocket.Tests/AspNetIntegrationTest.cs#L96
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Build:
test/SuperSocket.Tests/AspNetIntegrationTest.cs#L140
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Build:
test/SuperSocket.Tests/AspNetIntegrationTest.cs#L150
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Build:
test/SuperSocket.Tests/AspNetIntegrationTest.cs#L106
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Build:
test/SuperSocket.Tests/AspNetIntegrationTest.cs#L212
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
Loading