Skip to content

trigger api container release #56

trigger api container release

trigger api container release #56

Re-run triggered March 13, 2024 12:45
Status Success
Total duration 3m 38s
Artifacts

pipeline.yml

on: push
Build and test projects  /  determine-strategy
0s
Build and test projects / determine-strategy
Test staging area  /  determine-strategy
Test staging area / determine-strategy
Matrix: Build and test projects / build-and-test
Matrix: Test staging area / build-and-test
Waiting for pending jobs
Release API image
46s
Release API image
Release client package  /  release
Release client package / release
Release index package  /  release
Release index package / release
Staging area pre-publish checks
0s
Staging area pre-publish checks
Fit to window
Zoom out
Zoom in

Annotations

30 warnings
Build and test projects / build-and-test (ubuntu-latest): src/PackageRegistryService/Authentication/APIKeyEndpointFilter.cs#L13
Nullability of reference types in return type of 'ValueTask<object> APIKeyEndpointFilter.InvokeAsync(EndpointFilterInvocationContext context, EndpointFilterDelegate next)' doesn't match implicitly implemented member 'ValueTask<object?> IEndpointFilter.InvokeAsync(EndpointFilterInvocationContext context, EndpointFilterDelegate next)'.
Build and test projects / build-and-test (ubuntu-latest): src/PackageRegistryService/Pages/Handlers/IndexHandlers.cs#L9
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 and test projects / build-and-test (ubuntu-latest): src/PackageRegistryService/Pages/Handlers/AboutHandlers.cs#L9
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 and test projects / build-and-test (ubuntu-latest): src/PackageRegistryService/Data/DataInitializer.cs#L34
Possible null reference argument for parameter 'path1' in 'string Path.Combine(string path1, string path2)'.
Build and test projects / build-and-test (ubuntu-latest): src/PackageRegistryService/Data/DataInitializer.cs#L63
Possible null reference argument for parameter 'path1' in 'string Path.Combine(string path1, string path2)'.
Build and test projects / build-and-test (macos-latest): src/PackageRegistryService/Authentication/APIKeyEndpointFilter.cs#L13
Nullability of reference types in return type of 'ValueTask<object> APIKeyEndpointFilter.InvokeAsync(EndpointFilterInvocationContext context, EndpointFilterDelegate next)' doesn't match implicitly implemented member 'ValueTask<object?> IEndpointFilter.InvokeAsync(EndpointFilterInvocationContext context, EndpointFilterDelegate next)'.
Build and test projects / build-and-test (macos-latest): src/PackageRegistryService/Data/DataInitializer.cs#L34
Possible null reference argument for parameter 'path1' in 'string Path.Combine(string path1, string path2)'.
Build and test projects / build-and-test (macos-latest): src/PackageRegistryService/Data/DataInitializer.cs#L63
Possible null reference argument for parameter 'path1' in 'string Path.Combine(string path1, string path2)'.
Build and test projects / build-and-test (macos-latest): src/PackageRegistryService/Pages/Handlers/IndexHandlers.cs#L9
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 and test projects / build-and-test (macos-latest): src/PackageRegistryService/Pages/Handlers/AboutHandlers.cs#L9
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 and test projects / build-and-test (windows-latest): src/PackageRegistryService/Authentication/APIKeyEndpointFilter.cs#L13
Nullability of reference types in return type of 'ValueTask<object> APIKeyEndpointFilter.InvokeAsync(EndpointFilterInvocationContext context, EndpointFilterDelegate next)' doesn't match implicitly implemented member 'ValueTask<object?> IEndpointFilter.InvokeAsync(EndpointFilterInvocationContext context, EndpointFilterDelegate next)'.
Build and test projects / build-and-test (windows-latest): src/PackageRegistryService/Data/DataInitializer.cs#L34
Possible null reference argument for parameter 'path1' in 'string Path.Combine(string path1, string path2)'.
Build and test projects / build-and-test (windows-latest): src/PackageRegistryService/Data/DataInitializer.cs#L63
Possible null reference argument for parameter 'path1' in 'string Path.Combine(string path1, string path2)'.
Build and test projects / build-and-test (windows-latest): src/PackageRegistryService/Pages/Handlers/IndexHandlers.cs#L9
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 and test projects / build-and-test (windows-latest): src/PackageRegistryService/Pages/Handlers/AboutHandlers.cs#L9
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.