Skip to content

Add support for in-package frontmatter bindings: #73

Add support for in-package frontmatter bindings:

Add support for in-package frontmatter bindings: #73

Triggered via push April 25, 2024 07:39
Status Failure
Total duration 4m 22s
Artifacts

pipeline.yml

on: push
Build and test projects  /  determine-strategy
0s
Build and test projects / determine-strategy
Test staging area  /  determine-strategy
0s
Test staging area / determine-strategy
Matrix: Build and test projects / build-and-test
Matrix: Test staging area / build-and-test
Release API image
0s
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
update-preview-index
0s
update-preview-index
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 30 warnings
Test staging area / build-and-test (windows-latest): StagingAreaTests/Utils.fs#L24
The value, constructor, namespace or type 'frontMatterStart' is not defined. Maybe you want one of the following:� frontmatterBindingStart� frontMatterCommentStart� frontMatterCommentEnd� frontmatterBindingEnd
Test staging area / build-and-test (windows-latest): StagingAreaTests/Utils.fs#L25
The value, constructor, namespace or type 'frontMatterEnd' is not defined. Maybe you want one of the following:� frontMatterCommentEnd� frontmatterBindingEnd� frontMatterCommentStart� frontmatterBindingStart
Test staging area / build-and-test (windows-latest): StagingAreaTests/Utils.fs#L25
A unique overload for method 'Contains' could not be determined based on type information prior to this program point. A type annotation may be needed.��Known type of argument: 'a��Candidates:� - String.Contains(value: char) : bool� - String.Contains(value: string) : bool
Test staging area / build-and-test (windows-latest): StagingAreaTests/Utils.fs#L24
The value, constructor, namespace or type 'frontMatterStart' is not defined. Maybe you want one of the following:� frontmatterBindingStart� frontMatterCommentStart� frontMatterCommentEnd� frontmatterBindingEnd
Test staging area / build-and-test (windows-latest): StagingAreaTests/Utils.fs#L25
The value, constructor, namespace or type 'frontMatterEnd' is not defined. Maybe you want one of the following:� frontMatterCommentEnd� frontmatterBindingEnd� frontMatterCommentStart� frontmatterBindingStart
Test staging area / build-and-test (windows-latest): StagingAreaTests/Utils.fs#L25
A unique overload for method 'Contains' could not be determined based on type information prior to this program point. A type annotation may be needed.��Known type of argument: 'a��Candidates:� - String.Contains(value: char) : bool� - String.Contains(value: string) : bool
Test staging area / build-and-test (windows-latest)
Process completed with exit code 1.
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/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 (macos-latest): src/PackageRegistryService/Data/DataInitializer.cs#L35
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#L66
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/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/Data/DataInitializer.cs#L35
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#L66
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/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 (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#L35
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#L66
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.