Fix SK: RangeError: Maximum call stack size exceeded #21
myieyerelease-pipeline.yaml
on: push
Set Version
0s
Build API
/
publish-api
2m 23s
Build UI
/
publish-ui
2m 12s
Matrix: build-hgweb / deploy-hgweb / verify-published
Waiting for pending jobs
Matrix: Deploy Staging / verify-published
Matrix: Integration tests / test
Matrix: Deploy Production / verify-published
Deployment protection rules
Reviewers, timers, and other rules protecting deployments in this run
| Event | Environments |
|---|---|
myieye
approved
|
production |
Annotations
1 error and 47 warnings
|
Integration tests / Test ubuntu-latest on staging.languagedepot.org
Process completed with exit code 1.
|
|
Build API / publish-api:
backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
|
|
Build API / publish-api:
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.
|
|
Build API / publish-api:
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.
|
|
Build API / publish-api:
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.
|
|
Build API / publish-api:
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.
|
|
Build API / publish-api:
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.
|
|
Build API / publish-api:
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.
|
|
Build API / publish-api:
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.
|
|
Build API / publish-api:
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.
|
|
Build API / publish-api:
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.
|
|
Build API / publish-api
Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build API / publish-api
Non-nullable property 'Project' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build API / publish-api
Non-nullable property 'Node' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build API / publish-api
Non-nullable property 'Date' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build API / publish-api
Non-nullable property 'Desc' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build API / publish-api
Non-nullable property 'Branch' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build API / publish-api
Non-nullable property 'Tags' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build API / publish-api
Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build API / publish-api
Non-nullable property 'Phase' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build API / publish-api
Non-nullable property 'Parents' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Integration tests / Test ubuntu-latest on staging.languagedepot.org
The support for python 2.7 will be removed on June 19. Related issue: https://github.com/actions/setup-python/issues/672
|
|
Integration tests / Test ubuntu-latest on staging.languagedepot.org
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 / Test ubuntu-latest on staging.languagedepot.org:
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 / Test ubuntu-latest on staging.languagedepot.org:
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 / Test ubuntu-latest on staging.languagedepot.org:
backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
|
|
Integration tests / Test ubuntu-latest on staging.languagedepot.org:
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.
|
|
Integration tests / Test ubuntu-latest on staging.languagedepot.org:
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.
|
|
Integration tests / Test ubuntu-latest on staging.languagedepot.org:
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.
|
|
Integration tests / Test ubuntu-latest on staging.languagedepot.org:
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.
|
|
Integration tests / Test ubuntu-latest on staging.languagedepot.org:
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.
|
|
Integration tests / Test ubuntu-latest on staging.languagedepot.org:
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.
|
|
Integration tests / Test ubuntu-latest on staging.languagedepot.org:
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.
|
|
Integration tests / Test ubuntu-latest on staging.languagedepot.org:
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.
|
|
Integration tests / Test ubuntu-latest on staging.languagedepot.org:
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 / Test windows-latest on staging.languagedepot.org:
backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
|
|
Integration tests / Test windows-latest on staging.languagedepot.org:
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.
|
|
Integration tests / Test windows-latest on staging.languagedepot.org:
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.
|
|
Integration tests / Test windows-latest on staging.languagedepot.org:
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.
|
|
Integration tests / Test windows-latest on staging.languagedepot.org:
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.
|
|
Integration tests / Test windows-latest on staging.languagedepot.org:
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.
|
|
Integration tests / Test windows-latest on staging.languagedepot.org:
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.
|
|
Integration tests / Test windows-latest on staging.languagedepot.org:
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 / Test windows-latest on staging.languagedepot.org:
backend/LexCore/Entities/Project.cs#L83
Non-nullable property 'Parents' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Integration tests / Test windows-latest on staging.languagedepot.org:
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.
|
|
Integration tests / Test windows-latest on staging.languagedepot.org
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 / Test windows-latest on staging.languagedepot.org:
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 / Test windows-latest on staging.languagedepot.org:
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'
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
dotnet-unit-test-results
Expired
|
12.3 KB |
|
|
playwright-traces-ubuntu-latest
Expired
|
28 MB |
|
|
playwright-traces-windows-latest
Expired
|
28.3 MB |
|