Assert.IsInstanceOfType failed.

Test method DotVVM.Framework.Tests.ViewModel.JsonDiffTests.JsonDiff_Configuration_AddingRoute threw exception: Xunit.Sdk.ContainsException: Assert.Contains() Failure Not found: Route1 In value: SelectEnumerableIterator<RouteBase, String> []

Assert.AreEqual failed. Expected:<>. Actual:<{}>.

Test method DotVVM.Framework.Tests.Runtime.ConfigurationSerializationTests.SerializeDefaultConfig threw exception: System.Exception: ConfigurationSerializationTests.SerializeDefaultConfig.json has changed, the actual output differs from the previous accepted output: diff --git a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json index 0572bbf..7547369 100644 --- a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json +++ b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeDefaultConfig.json @@ -131,6 +131,7 @@ }, "security": {}, "runtime": {}, + "defaultCulture": "en-US", "experimentalFeatures": { "explicitAssemblyLoading": { "enabled": true Is this change OK? To let the test pass, stage the file in git. Confused? See https://github.com/exyi/CheckTestOutput/blob/master/trouble.md#changed-file

Test method DotVVM.Framework.Tests.Runtime.ConfigurationSerializationTests.SerializeEmptyConfig threw exception: System.Exception: ConfigurationSerializationTests.SerializeEmptyConfig.json has changed, the actual output differs from the previous accepted output: diff --git a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeEmptyConfig.json b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeEmptyConfig.json index 087ce44..c8ca659 100644 --- a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeEmptyConfig.json +++ b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeEmptyConfig.json @@ -7,6 +7,7 @@ "resources": {}, "security": {}, "runtime": {}, + "defaultCulture": "en-US", "experimentalFeatures": {}, "diagnostics": { "compilationPage": {}, Is this change OK? To let the test pass, stage the file in git. Confused? See https://github.com/exyi/CheckTestOutput/blob/master/trouble.md#changed-file

Test method DotVVM.Framework.Tests.Runtime.ConfigurationSerializationTests.SerializeRoutes threw exception: System.Exception: ConfigurationSerializationTests.SerializeRoutes.json has changed, the actual output differs from the previous accepted output: diff --git a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeRoutes.json b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeRoutes.json index 8cc72ac..ed68565 100644 --- a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeRoutes.json +++ b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeRoutes.json @@ -38,6 +38,7 @@ "resources": {}, "security": {}, "runtime": {}, + "defaultCulture": "en-US", "experimentalFeatures": {}, "diagnostics": { "compilationPage": {}, Is this change OK? To let the test pass, stage the file in git. Confused? See https://github.com/exyi/CheckTestOutput/blob/master/trouble.md#changed-file

Test method DotVVM.Framework.Tests.Runtime.ConfigurationSerializationTests.SerializeResources threw exception: System.Exception: ConfigurationSerializationTests.SerializeResources.json has changed, the actual output differs from the previous accepted output: diff --git a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeResources.json b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeResources.json index a40e91c..11eac35 100644 --- a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeResources.json +++ b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.SerializeResources.json @@ -83,6 +83,7 @@ }, "security": {}, "runtime": {}, + "defaultCulture": "en-US", "experimentalFeatures": {}, "diagnostics": { "compilationPage": {}, Is this change OK? To let the test pass, stage the file in git. Confused? See https://github.com/exyi/CheckTestOutput/blob/master/trouble.md#changed-file

Test method DotVVM.Framework.Tests.Runtime.ConfigurationSerializationTests.ExperimentalFeatures threw exception: System.Exception: ConfigurationSerializationTests.ExperimentalFeatures.json has changed, the actual output differs from the previous accepted output: diff --git a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.ExperimentalFeatures.json b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.ExperimentalFeatures.json index 5a75ebd..2c9f447 100644 --- a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.ExperimentalFeatures.json +++ b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.ExperimentalFeatures.json @@ -7,6 +7,7 @@ "resources": {}, "security": {}, "runtime": {}, + "defaultCulture": "en-US", "experimentalFeatures": { "lazyCsrfToken": { "enabled": true, Is this change OK? To let the test pass, stage the file in git. Confused? See https://github.com/exyi/CheckTestOutput/blob/master/trouble.md#changed-file

Test method DotVVM.Framework.Tests.Runtime.ConfigurationSerializationTests.Markup threw exception: System.Exception: ConfigurationSerializationTests.Markup.json has changed, the actual output differs from the previous accepted output: diff --git a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.Markup.json b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.Markup.json index 986568c..458e2a1 100644 --- a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.Markup.json +++ b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.Markup.json @@ -57,6 +57,7 @@ "resources": {}, "security": {}, "runtime": {}, + "defaultCulture": "en-US", "experimentalFeatures": {}, "diagnostics": { "compilationPage": {}, Is this change OK? To let the test pass, stage the file in git. Confused? See https://github.com/exyi/CheckTestOutput/blob/master/trouble.md#changed-file

Test method DotVVM.Framework.Tests.Runtime.ConfigurationSerializationTests.RestAPI threw exception: System.Exception: ConfigurationSerializationTests.RestAPI.json has changed, the actual output differs from the previous accepted output: diff --git a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.RestAPI.json b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.RestAPI.json index bb8b049..1bb8652 100644 --- a/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.RestAPI.json +++ b/src/Tests/Runtime/config-tests/ConfigurationSerializationTests.RestAPI.json @@ -40,6 +40,7 @@ }, "security": {}, "runtime": {}, + "defaultCulture": "en-US", "experimentalFeatures": {}, "diagnostics": { "compilationPage": {}, Is this change OK? To let the test pass, stage the file in git. Confused? See https://github.com/exyi/CheckTestOutput/blob/master/trouble.md#changed-file

Action failed since 520 tests failed.

Process completed with exit code 1.

Process completed with exit code 1.

Assert.IsInstanceOfType failed.

Test method DotVVM.Framework.Tests.ViewModel.JsonDiffTests.JsonDiff_Configuration_AddingRoute threw exception: Xunit.Sdk.ContainsException: Assert.Contains() Failure Not found: Route1 In value: SelectEnumerableIterator<RouteBase, String> []

Assert.AreEqual failed. Expected:<>. Actual:<{}>.

Test method DotVVM.Framework.Tests.Runtime.DotvvmCompilationExceptionSerializationTests.DotvvmCompilationException_SerializationAndDeserialization_WorksCorrectly threw exception: System.NotSupportedException: Deserialization of types without a parameterless constructor, a singular parameterized constructor, or a parameterized constructor annotated with 'JsonConstructorAttribute' is not supported. Type 'DotVVM.Framework.Compilation.DotvvmCompilationException'. Path: $ | LineNumber: 0 | BytePositionInLine: 1. ---> System.NotSupportedException: Deserialization of types without a parameterless constructor, a singular parameterized constructor, or a parameterized constructor annotated with 'JsonConstructorAttribute' is not supported. Type 'DotVVM.Framework.Compilation.DotvvmCompilationException'.

Test method DotVVM.Framework.Tests.Runtime.ErrorPageTests.InvalidBindingException threw exception: System.NotSupportedException: Serialization and deserialization of 'System.Reflection.MethodBase' instances is not supported. Path: $.TargetSite. ---> System.NotSupportedException: Serialization and deserialization of 'System.Reflection.MethodBase' instances is not supported.

Assert.IsTrue failed.

Assert.IsTrue failed.

Test method DotVVM.Framework.Tests.Routing.RouteSerializationTests.RouteTable_Deserialization threw exception: System.ArgumentException: The route with name 'route1' does not exist!

Test method DotVVM.Framework.Tests.ControlTests.SimpleControlTests.Literal_ClientServerRendering threw exception: System.Exception: SimpleControlTests.Literal_ClientServerRendering.html has changed, the actual output differs from the previous accepted output: diff --git a/src/Tests/ControlTests/testoutputs/SimpleControlTests.Literal_ClientServerRendering.html b/src/Tests/ControlTests/testoutputs/SimpleControlTests.Literal_ClientServerRendering.html index ef489d7..e206ab2 100644 --- a/src/Tests/ControlTests/testoutputs/SimpleControlTests.Literal_ClientServerRendering.html +++ b/src/Tests/ControlTests/testoutputs/SimpleControlTests.Literal_ClientServerRendering.html @@ -6,7 +6,7 @@ <span data-bind="text: dotvvm.globalize.bindingNumberToString(int)() + &quot;\n &quot; + dotvvm.globalize.bindingNumberToString(float)() + &quot;\n &quot; + (dotvvm.globalize.bindingDateToString(date)() ?? &quot;&quot;) + &quot;\n &quot; + (NullableString() ?? &quot;&quot;)"></span> <!-- literal syntax, server rendering --> - <span data-bind="text: dotvvm.globalize.bindingNumberToString(int)() + &quot;\n &quot; + dotvvm.globalize.bindingNumberToString(float)() + &quot;\n &quot; + (dotvvm.globalize.bindingDateToString(date)() ?? &quot;&quot;) + &quot;\n &quot; + (NullableString() ?? &quot;&quot;)">10000000 0.11111 8/11/2020 4:01:44 PM + <span data-bind="text: dotvvm.globalize.bindingNumberToString(int)() + &quot;\n &quot; + dotvvm.globalize.bindingNumberToString(float)() + &quot;\n &quot; + (dotvvm.globalize.bindingDateToString(date)() ?? &quot;&quot;) + &quot;\n &quot; + (NullableString() ?? &quot;&quot;)">10000000 0.11111 8/11/2020 4:01:44 PM </span> <!-- control syntax, client rendering --> @@ -20,7 +20,7 @@ <span> <span data-bind="text: int">10000000</span> <span data-bind="text: dotvvm.globalize.formatString(&quot;&quot;, float, &quot;double&quot;)">0.11111</span> - <span data-bind="text: dotvvm.globalize.formatString(&quot;&quot;, date, &quot;datetime&quot;)">8/11/2020 4:01:44 PM</span> + <span data-bind="text: dotvvm.globalize.formatString(&quot;&quot;, date, &quot;datetime&quot;)">8/11/2020 4:01:44 PM</span> </span> <!-- control syntax, client rendering, format string --> Is this change OK? To let the test pass, stage the file in git. Confused? See https://github.com/exyi/CheckTestOutput/blob/master/trouble.md#changed-file

Process completed with exit code 1.

Process completed with exit code 1.

Assert.IsInstanceOfType failed.

Test method DotVVM.Framework.Tests.ViewModel.JsonDiffTests.JsonDiff_Configuration_AddingRoute threw exception: Xunit.Sdk.ContainsException: Assert.Contains() Failure Not found: Route1 In value: SelectEnumerableIterator<RouteBase, String> []

Assert.AreEqual failed. Expected:<>. Actual:<{}>.

Test method DotVVM.Framework.Tests.Runtime.DotvvmCompilationExceptionSerializationTests.DotvvmCompilationException_SerializationAndDeserialization_WorksCorrectly threw exception: System.NotSupportedException: Deserialization of types without a parameterless constructor, a singular parameterized constructor, or a parameterized constructor annotated with 'JsonConstructorAttribute' is not supported. Type 'DotVVM.Framework.Compilation.DotvvmCompilationException'. Path: $ | LineNumber: 0 | BytePositionInLine: 1. ---> System.NotSupportedException: Deserialization of types without a parameterless constructor, a singular parameterized constructor, or a parameterized constructor annotated with 'JsonConstructorAttribute' is not supported. Type 'DotVVM.Framework.Compilation.DotvvmCompilationException'.

Test method DotVVM.Framework.Tests.Runtime.ErrorPageTests.InvalidBindingException threw exception: System.NotSupportedException: Serialization and deserialization of 'System.Reflection.MethodBase' instances is not supported. Path: $.TargetSite. ---> System.NotSupportedException: Serialization and deserialization of 'System.Reflection.MethodBase' instances is not supported.

Assert.IsTrue failed.

Assert.IsTrue failed.

Test method DotVVM.Framework.Tests.Routing.RouteSerializationTests.RouteTable_Deserialization threw exception: System.ArgumentException: The route with name 'route1' does not exist!

Test method DotVVM.Framework.Tests.ControlTests.SimpleControlTests.Literal_ClientServerRendering threw exception: System.Exception: SimpleControlTests.Literal_ClientServerRendering.html has changed, the actual output differs from the previous accepted output: diff --git a/src/Tests/ControlTests/testoutputs/SimpleControlTests.Literal_ClientServerRendering.html b/src/Tests/ControlTests/testoutputs/SimpleControlTests.Literal_ClientServerRendering.html index ef489d7..e206ab2 100644 --- a/src/Tests/ControlTests/testoutputs/SimpleControlTests.Literal_ClientServerRendering.html +++ b/src/Tests/ControlTests/testoutputs/SimpleControlTests.Literal_ClientServerRendering.html @@ -6,7 +6,7 @@ <span data-bind="text: dotvvm.globalize.bindingNumberToString(int)() + &quot;\n &quot; + dotvvm.globalize.bindingNumberToString(float)() + &quot;\n &quot; + (dotvvm.globalize.bindingDateToString(date)() ?? &quot;&quot;) + &quot;\n &quot; + (NullableString() ?? &quot;&quot;)"></span> <!-- literal syntax, server rendering --> - <span data-bind="text: dotvvm.globalize.bindingNumberToString(int)() + &quot;\n &quot; + dotvvm.globalize.bindingNumberToString(float)() + &quot;\n &quot; + (dotvvm.globalize.bindingDateToString(date)() ?? &quot;&quot;) + &quot;\n &quot; + (NullableString() ?? &quot;&quot;)">10000000 0.11111 8/11/2020 4:01:44 PM + <span data-bind="text: dotvvm.globalize.bindingNumberToString(int)() + &quot;\n &quot; + dotvvm.globalize.bindingNumberToString(float)() + &quot;\n &quot; + (dotvvm.globalize.bindingDateToString(date)() ?? &quot;&quot;) + &quot;\n &quot; + (NullableString() ?? &quot;&quot;)">10000000 0.11111 8/11/2020 4:01:44 PM </span> <!-- control syntax, client rendering --> @@ -20,7 +20,7 @@ <span> <span data-bind="text: int">10000000</span> <span data-bind="text: dotvvm.globalize.formatString(&quot;&quot;, float, &quot;double&quot;)">0.11111</span> - <span data-bind="text: dotvvm.globalize.formatString(&quot;&quot;, date, &quot;datetime&quot;)">8/11/2020 4:01:44 PM</span> + <span data-bind="text: dotvvm.globalize.formatString(&quot;&quot;, date, &quot;datetime&quot;)">8/11/2020 4:01:44 PM</span> </span> <!-- control syntax, client rendering, format string --> Is this change OK? To let the test pass, stage the file in git. Confused? See https://github.com/exyi/CheckTestOutput/blob/master/trouble.md#changed-file

Process completed with exit code 1.

Action failed since 37 tests failed.

Process completed with exit code 1.

Action failed since 76 tests failed.

Process completed with exit code 1.

The job running on runner GitHub Actions 7 has exceeded the maximum execution time of 50 minutes.

The job running on runner GitHub Actions 17 has exceeded the maximum execution time of 50 minutes.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, nuget/setup-nuget@v1, actions/cache@v3, actions/setup-node@v3, actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, nuget/setup-nuget@v1, actions/cache@v3, actions/setup-node@v3, actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)

Do not use Assert.Equal() to check for collection size. Use Assert.Empty instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)

Do not use Assert.Equal() to check for collection size. Use Assert.Single instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)

Do not use Assert.Equal() to check for collection size. Use Assert.Single instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)

Do not use Assert.Equal() to check for collection size. Use Assert.Empty instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)

Do not use Assert.Equal() to check for collection size. Use Assert.Empty instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, nuget/setup-nuget@v1, actions/cache@v3, actions/setup-node@v3, actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, nuget/setup-nuget@v1, actions/cache@v3, actions/setup-node@v3, actions/setup-dotnet@v3, microsoft/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, nuget/setup-nuget@v1, actions/cache@v3, actions/setup-node@v3, actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, nuget/setup-nuget@v1, actions/cache@v3, actions/setup-node@v3, actions/setup-dotnet@v3, microsoft/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, nuget/setup-nuget@v1, actions/cache@v3, actions/setup-node@v3, actions/setup-dotnet@v3, microsoft/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)

Do not use Assert.Equal() to check for collection size. Use Assert.Empty instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)

Do not use Assert.Equal() to check for collection size. Use Assert.Empty instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)

Do not use Assert.Equal() to check for collection size. Use Assert.Single instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)

Do not use Assert.Equal() to check for collection size. Use Assert.Single instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)

Do not use Assert.Equal() to check for collection size. Use Assert.Empty instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

The target framework 'netcoreapp3.1' 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.

Do not use Assert.Equal() to check for collection size. Use Assert.Empty instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)

Do not use Assert.Equal() to check for collection size. Use Assert.Empty instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)

Do not use Assert.Equal() to check for collection size. Use Assert.Single instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)

Do not use Assert.Equal() to check for collection size. Use Assert.Empty instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)

Do not use Assert.Equal() to check for collection size. Use Assert.Single instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)