Skip to content

Connection string parts validation (#276) #284

Connection string parts validation (#276)

Connection string parts validation (#276) #284

Triggered via push September 20, 2024 10:46
Status Success
Total duration 7m 28s
Artifacts
Matrix: Analyze
Fit to window
Zoom out
Zoom in

Annotations

13 warnings
Analyze (csharp)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Analyze (csharp)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, github/codeql-action/init@v2, actions/setup-dotnet@v1, github/codeql-action/analyze@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Analyze (csharp): test/UnitTests/Core/NBB.Core.Pipeline.Tests/PipelineTests.cs#L178
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
Analyze (csharp): src/Messaging/NBB.Messaging.Noop/NoopTransportMonitor.cs#L12
The field 'NoopTransportMonitor.OnError' is assigned but its value is never used
Analyze (csharp): test/UnitTests/MultiTenancy/NBB.MultiTenancy.Identification.Tests/Identifiers/IdTenantIdentifierTests.cs#L21
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
Analyze (csharp): test/UnitTests/MultiTenancy/NBB.MultiTenancy.Identification.Tests/Services/TenantServiceTests.cs#L43
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
Analyze (csharp): test/UnitTests/MultiTenancy/NBB.MultiTenancy.Identification.Tests/Services/TenantServiceTests.cs#L63
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
Analyze (csharp): test/UnitTests/MultiTenancy/NBB.MultiTenancy.Identification.Tests/Services/TenantServiceTests.cs#L80
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
Analyze (csharp): test/UnitTests/MultiTenancy/NBB.MultiTenancy.Identification.Tests/Services/TenantServiceTests.cs#L100
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
Analyze (csharp): test/UnitTests/Data/NBB.Data.EntityFramework.MultiTenancy.Tests/MultiTenancyTests.cs#L66
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
Analyze (csharp): test/UnitTests/MultiTenancy/NBB.MultiTenancy.Identification.Messaging.Tests/TenantIdHeaderMessagingTokenResolverTests.cs#L36
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
Analyze (csharp): test/UnitTests/MultiTenancy/NBB.MultiTenancy.Identification.Messaging.Tests/TenantIdHeaderMessagingTokenResolverTests.cs#L50
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
Analyze (csharp)
CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/