Skip to content

bit platform full CI #58

bit platform full CI

bit platform full CI #58

Manually triggered June 8, 2024 19:59
Status Success
Total duration 28m 48s
Artifacts

bit.full.ci.yml

on: workflow_dispatch
Fit to window
Zoom out
Zoom in

Annotations

1 error and 49 warnings
build and test
Process completed with exit code 1.
build and test
Some target frameworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below:
build and test
- Add lib or ref assemblies for the net8.0 target framework
build and test
Some target frameworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below:
build and test
- Add lib or ref assemblies for the net8.0 target framework
build and test
Some target frameworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below:
build and test
- Add lib or ref assemblies for the net8.0 target framework
build and test: src/CodeAnalyzers/Bit.CodeAnalyzers/Extensions/ISymbolExtensions.cs#L47
Dereference of a possibly null reference.
build and test: src/CodeAnalyzers/Bit.CodeAnalyzers/SystemAnalyzers/DateTimeOffsetInsteadOfDateTimeAnalyzer.cs#L42
Converting null literal or possible null value to non-nullable type.
build and test: src/CodeAnalyzers/Bit.CodeAnalyzers/SystemCodeFixes/DateTimeOffsetInsteadOfDateTimeCodeFixProvider.cs#L49
The type 'Microsoft.CodeAnalysis.SyntaxNode?' cannot be used as type parameter 'TRoot' in the generic type or method 'SyntaxNodeExtensions.ReplaceNode<TRoot>(TRoot, SyntaxNode, SyntaxNode)'. Nullability of type argument 'Microsoft.CodeAnalysis.SyntaxNode?' doesn't match constraint type 'Microsoft.CodeAnalysis.SyntaxNode'.
build and test: src/CodeAnalyzers/Bit.CodeAnalyzers/SystemCodeFixes/DateTimeOffsetInsteadOfDateTimeCodeFixProvider.cs#L49
Possible null reference argument for parameter 'newNode' in 'SyntaxNode? SyntaxNodeExtensions.ReplaceNode<SyntaxNode?>(SyntaxNode? root, SyntaxNode oldNode, SyntaxNode newNode)'.
build and test: src/CodeAnalyzers/Bit.CodeAnalyzers/SystemCodeFixes/DateTimeOffsetInsteadOfDateTimeCodeFixProvider.cs#L51
Possible null reference argument for parameter 'root' in 'Document Document.WithSyntaxRoot(SyntaxNode root)'.
build and test: src/CodeAnalyzers/Bit.CodeAnalyzers/SystemCodeFixes/ClassWithoutModifierCodeFixProvider.cs#L49
The type 'Microsoft.CodeAnalysis.SyntaxNode?' cannot be used as type parameter 'TRoot' in the generic type or method 'SyntaxNodeExtensions.ReplaceNode<TRoot>(TRoot, SyntaxNode, SyntaxNode)'. Nullability of type argument 'Microsoft.CodeAnalysis.SyntaxNode?' doesn't match constraint type 'Microsoft.CodeAnalysis.SyntaxNode'.
build and test: src/CodeAnalyzers/Bit.CodeAnalyzers/SystemCodeFixes/ClassWithoutModifierCodeFixProvider.cs#L49
Possible null reference argument for parameter 'newNode' in 'SyntaxNode? SyntaxNodeExtensions.ReplaceNode<SyntaxNode?>(SyntaxNode? root, SyntaxNode oldNode, SyntaxNode newNode)'.
build and test: src/CodeAnalyzers/Bit.CodeAnalyzers/SystemCodeFixes/ClassWithoutModifierCodeFixProvider.cs#L51
Possible null reference argument for parameter 'root' in 'Document Document.WithSyntaxRoot(SyntaxNode root)'.
build and test
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
build and test
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
build and test: ApiFalse/src/Client/ApiFalse.Client.Core/Components/Layout/MainLayout.razor.cs#L11
The field 'MainLayout.errorBoundaryRef' is assigned but its value is never used
build and test: ApiFalse/src/Client/ApiFalse.Client.Core/Services/Contracts/IPrerenderStateService.cs#L15
Ambiguous reference in cref attribute: 'GetValue'. Assuming 'IPrerenderStateService.GetValue<T>(Func<Task<T?>>, int, string, string)', but could have also matched other overloads including 'IPrerenderStateService.GetValue<T>(string, Func<Task<T?>>)'.
build and test: ApiFalse/src/Client/ApiFalse.Client.Core/Components/Layout/SignOutConfirmModal.razor.cs#L8
Component parameter 'ApiFalse.Client.Core.Components.Layout.SignOutConfirmModal.IsOpen' should be auto property
build and test: ApiFalse/src/Client/ApiFalse.Client.Core/Components/Pages/Identity/Profile/UserDataSection.razor.cs#L30
Component parameter 'ApiFalse.Client.Core.Components.Pages.Identity.Profile.UserDataSection.User' should be auto property
build and test: ApiFalse/src/Client/ApiFalse.Client.Maui/Services/MauiDeviceCoordinator.cs#L35
This call site is reachable on: 'Android' 24.0 and later. 'View.SystemUiFlags' is obsoleted on: 'Android' 30.0 and later (These flags are deprecated. Use WindowInsetsController instead.). (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1422)
build and test: ApiFalse/src/Client/ApiFalse.Client.Maui/Services/MauiDeviceCoordinator.cs#L32
This call site is reachable on: 'Android' 24.0 and later. 'View.SystemUiFlags' is obsoleted on: 'Android' 30.0 and later (These flags are deprecated. Use WindowInsetsController instead.). (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1422)
build and test
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
build and test
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
build and test
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
build and test
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
build and test
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
build and test: EmptyBP/src/Client/EmptyBP.Client.Core/Components/Layout/MainLayout.razor.cs#L11
The field 'MainLayout.errorBoundaryRef' is assigned but its value is never used
build and test: EmptyBP/src/Client/EmptyBP.Client.Core/Services/Contracts/IPrerenderStateService.cs#L15
Ambiguous reference in cref attribute: 'GetValue'. Assuming 'IPrerenderStateService.GetValue<T>(Func<Task<T?>>, int, string, string)', but could have also matched other overloads including 'IPrerenderStateService.GetValue<T>(string, Func<Task<T?>>)'.
build and test: EmptyBP/src/Client/EmptyBP.Client.Core/Components/Layout/SignOutConfirmModal.razor.cs#L8
Component parameter 'EmptyBP.Client.Core.Components.Layout.SignOutConfirmModal.IsOpen' should be auto property
build and test: EmptyBP/src/Client/EmptyBP.Client.Core/Components/Pages/Identity/Profile/UserDataSection.razor.cs#L30
Component parameter 'EmptyBP.Client.Core.Components.Pages.Identity.Profile.UserDataSection.User' should be auto property
build and test
Found a native function (sqlite3_config) with varargs in e_sqlite3. Calling such functions is not supported, and will fail at runtime. Managed DllImports:
build and test
System.Int32 sqlite3_config_none(System.Int32) (in
build and test
System.Int32 sqlite3_config_int(System.Int32, System.Int32) (in
build and test: src/BlazorUI/Demo/Bit.BlazorUI.Demo.Shared/Dtos/ComponentPropertyDetailsDto.cs#L5
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
build and test: src/BlazorUI/Demo/Bit.BlazorUI.Demo.Shared/Dtos/ComponentPropertyDetailsDto.cs#L6
Non-nullable property 'DefaultValue' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
build and test: src/BlazorUI/Demo/Bit.BlazorUI.Demo.Shared/Dtos/ComponentPropertyDetailsDto.cs#L7
Non-nullable property 'Type' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
build and test: src/BlazorUI/Demo/Bit.BlazorUI.Demo.Shared/Dtos/ComponentPropertyDetailsDto.cs#L8
Non-nullable property 'Description' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
build and test: src/BlazorUI/Demo/Bit.BlazorUI.Demo.Shared/Dtos/ComponentMethodDetailsDto.cs#L5
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
build and test: src/BlazorUI/Demo/Bit.BlazorUI.Demo.Shared/Dtos/ComponentMethodDetailsDto.cs#L6
Non-nullable property 'Parameters' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
build and test: src/BlazorUI/Demo/Bit.BlazorUI.Demo.Shared/Dtos/ComponentMethodDetailsDto.cs#L7
Non-nullable property 'Output' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
build and test: src/BlazorUI/Demo/Bit.BlazorUI.Demo.Shared/Dtos/ComponentMethodDetailsDto.cs#L8
Non-nullable property 'Summary' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
build and test: src/BlazorUI/Bit.BlazorUI/Components/Persona/BitPersona.razor.cs#L308
The switch expression does not handle some values of its input type (it is not exhaustive) involving an unnamed enum value. For example, the pattern '(Bit.BlazorUI.BitPersonaSize)9' is not covered.
build and test
Some target frameworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below:
build and test
- Add lib or ref assemblies for the net8.0 target framework
build and test
Some target frameworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below: