Migrated Roslyn Analyzers and Generators to netstandard20 #171
Annotations
21 warnings
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@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/.
|
|
Build for Azure Deploy:
src/Application.Common.UnitTests/Extensions/FeatureFlagExtensionsSpec.cs#L37
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build for Azure Deploy:
src/Application.Common.UnitTests/Extensions/FeatureFlagExtensionsSpec.cs#L52
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build for Azure Deploy:
src/Application.Common.UnitTests/Extensions/FeatureFlagExtensionsSpec.cs#L67
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build for Azure Deploy:
src/Infrastructure.Web.Api.Common.UnitTests/Endpoints/ApiUsageFilterSpec.cs#L74
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build for Azure Deploy:
src/Infrastructure.Shared.IntegrationTests/ApplicationServices/External/FlagsmithHttpServiceClientSpec.cs#L39
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build for Azure Deploy:
src/Infrastructure.Shared.IntegrationTests/ApplicationServices/External/FlagsmithHttpServiceClientSpec.cs#L62
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build for Azure Deploy:
src/Infrastructure.Shared.IntegrationTests/ApplicationServices/External/FlagsmithHttpServiceClientSpec.cs#L75
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build for Azure Deploy:
src/Infrastructure.Shared.IntegrationTests/ApplicationServices/External/FlagsmithHttpServiceClientSpec.cs#L88
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build for Azure Deploy:
src/Infrastructure.Shared.IntegrationTests/ApplicationServices/External/FlagsmithHttpServiceClientSpec.cs#L101
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build for Azure Deploy:
src/Infrastructure.Shared.IntegrationTests/ApplicationServices/External/FlagsmithHttpServiceClientSpec.cs#L115
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build for AWS Deploy:
src/Application.Common.UnitTests/Extensions/FeatureFlagExtensionsSpec.cs#L37
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build for AWS Deploy:
src/Application.Common.UnitTests/Extensions/FeatureFlagExtensionsSpec.cs#L52
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build for AWS Deploy:
src/Application.Common.UnitTests/Extensions/FeatureFlagExtensionsSpec.cs#L67
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build for AWS Deploy:
src/Infrastructure.Web.Api.Common.UnitTests/Endpoints/ApiUsageFilterSpec.cs#L74
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build for AWS Deploy:
src/Infrastructure.Web.Hosting.Common.UnitTests/Pipeline/CSRFServiceSpec.cs#L27
Possible null reference argument for parameter 'encryptionService' in 'CSRFService.CSRFService(IHostSettings settings, IEncryptionService encryptionService)'.
|
|
Build for AWS Deploy:
src/Infrastructure.Web.Hosting.Common.UnitTests/Pipeline/CSRFTokenPairSpec.cs#L16
Non-nullable field '_encryptionService' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
|
Build for AWS Deploy:
src/Infrastructure.Web.Hosting.Common.UnitTests/Pipeline/CSRFServiceSpec.cs#L15
Field 'CSRFServiceSpec._encryptionService' is never assigned to, and will always have its default value null
|
|
Build for AWS Deploy:
src/Infrastructure.Web.Hosting.Common.UnitTests/Pipeline/CSRFTokenPairSpec.cs#L14
Field 'CSRFTokenPairSpec._encryptionService' is never assigned to, and will always have its default value null
|
|
Build for AWS Deploy:
src/Infrastructure.Shared.IntegrationTests/ApplicationServices/External/FlagsmithHttpServiceClientSpec.cs#L39
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build for AWS Deploy:
src/Infrastructure.Shared.IntegrationTests/ApplicationServices/External/FlagsmithHttpServiceClientSpec.cs#L62
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
The logs for this run have expired and are no longer available.
Loading