catch errors that may occur when updating last commit date during #24
Annotations
19 warnings
|
Dotnet build:
backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
|
|
Dotnet build:
backend/LexCore/Entities/ProjectUsers.cs#L8
Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/ProjectUsers.cs#L9
Non-nullable property 'Project' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/Project.cs#L72
Non-nullable property 'Node' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/Project.cs#L73
Non-nullable property 'Date' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/Project.cs#L74
Non-nullable property 'Desc' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/Project.cs#L76
Non-nullable property 'Branch' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/Project.cs#L80
Non-nullable property 'Tags' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/Project.cs#L81
Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/Project.cs#L82
Non-nullable property 'Phase' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Integration tests
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
|
Integration tests:
backend/LexBoxApi/Auth/LexboxAuthAttribute.cs#L15
Nullability of reference types in type of parameter 'value' of 'void LexboxAuthAttribute.Policy.set' doesn't match implicitly implemented member 'void IAuthorizeData.Policy.set' (possibly because of nullability attributes).
|
|
Integration tests:
backend/LexBoxApi/Auth/JwtTicketDataFormat.cs#L115
'JwtBearerOptions.SecurityTokenValidators' is obsolete: 'SecurityTokenValidators is no longer used by default. Use TokenHandlers instead. To continue using SecurityTokenValidators, set UseSecurityTokenValidators to true. See https://aka.ms/aspnetcore8/security-token-changes'
|
|
Integration tests:
backend/Testing/SyncReverseProxy/SendReceiveServiceTests.cs#L158
Dereference of a possibly null reference.
|
|
Integration tests:
backend/Testing/SyncReverseProxy/SendReceiveServiceTests.cs#L158
Dereference of a possibly null reference.
|
|
Integration tests:
backend/Testing/SyncReverseProxy/SendReceiveServiceTests.cs#L158
Dereference of a possibly null reference.
|
|
Integration tests:
backend/Testing/SyncReverseProxy/SendReceiveServiceTests.cs#L176
Dereference of a possibly null reference.
|
|
Integration tests:
backend/Testing/SyncReverseProxy/SendReceiveServiceTests.cs#L176
Dereference of a possibly null reference.
|
|
Integration tests:
backend/Testing/SyncReverseProxy/SendReceiveServiceTests.cs#L176
Dereference of a possibly null reference.
|
The logs for this run have expired and are no longer available.
Loading