Skip to content

correct LfClassicData.csproj path that references MiniLcm.csproj #954

correct LfClassicData.csproj path that references MiniLcm.csproj

correct LfClassicData.csproj path that references MiniLcm.csproj #954

Triggered via push July 10, 2024 04:41
Status Failure
Total duration 18m 54s
Artifacts

develop-api.yaml

on: push
Set Version
1s
Set Version
Build API  /  publish-api
3m 10s
Build API / publish-api
Deploy API  /  deploy
18s
Deploy API / deploy
Matrix: Deploy API / verify-published
Integration tests  /  Dotnet tests on self-hosted for Mercurial 6 on develop
13m 51s
Integration tests / Dotnet tests on self-hosted for Mercurial 6 on develop
Integration tests  /  Playwright tests on self-hosted for Mercurial 6 on develop
10m 41s
Integration tests / Playwright tests on self-hosted for Mercurial 6 on develop
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 41 warnings
Integration tests / Playwright tests on self-hosted for Mercurial 6 on develop
Process completed with exit code 137.
Integration tests / Playwright tests on self-hosted for Mercurial 6 on develop
Process completed with exit code 1.
Integration tests / Dotnet tests on self-hosted for Mercurial 6 on develop
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/FwLite/MiniLcm/InMemoryApi.cs#L195
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 API / publish-api: backend/FwLite/MiniLcm/InMemoryApi.cs#L214
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 API / publish-api: backend/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L167
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 API / publish-api: backend/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L175
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 API / publish-api: backend/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L255
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 API / publish-api: backend/FwLite/FwDataMiniLcmBridge/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
Build API / publish-api: backend/FwLite/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateEntryProxy.cs#L38
Observe the awaitable result of this method call by awaiting it, assigning to a variable, or passing it to another method (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD110.md)
Build API / publish-api: backend/FwLite/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateSenseProxy.cs#L89
Observe the awaitable result of this method call by awaiting it, assigning to a variable, or passing it to another method (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD110.md)
Build API / publish-api: backend/LfClassicData/LfClassicLexboxApi.cs#L191
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 API / publish-api
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 API / publish-api
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 API / publish-api
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 API / publish-api
Parameter 'logger' is unread.
Build API / publish-api
Parameter 'lexAuthService' is unread.
Build API / publish-api
Parameter 'hgService' is unread.
Build API / publish-api
'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'
Build API / publish-api
Parameter 'lexAuthService' is unread.
Build API / publish-api
Parameter 'lexBoxDbContext' is unread.
Build API / publish-api
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 '(LexBoxApi.Services.RepoEmptyState)2' is not covered.
Build API / publish-api
No files were found with the provided path: ./test-results. No artifacts will be uploaded.
Integration tests / Dotnet tests on self-hosted for Mercurial 6 on develop: backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
Integration tests / Dotnet tests on self-hosted for Mercurial 6 on develop: backend/FwLite/MiniLcm/InMemoryApi.cs#L195
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.
Integration tests / Dotnet tests on self-hosted for Mercurial 6 on develop: backend/FwLite/MiniLcm/InMemoryApi.cs#L214
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.
Integration tests / Dotnet tests on self-hosted for Mercurial 6 on develop: backend/FwLite/LcmCrdt/LcmCrdtKernel.cs#L4
The using directive for 'Crdt' appeared previously in this namespace
Integration tests / Dotnet tests on self-hosted for Mercurial 6 on develop: backend/FwLite/LcmCrdt/Changes/RemoveSemanticDomainChange.cs#L11
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.
Integration tests / Dotnet tests on self-hosted for Mercurial 6 on develop: backend/FwLite/LcmCrdt/Changes/CreatePartOfSpeechChange.cs#L15
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.
Integration tests / Dotnet tests on self-hosted for Mercurial 6 on develop: backend/FwLite/LcmCrdt/Changes/CreateSemanticDomainChange.cs#L16
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.
Integration tests / Dotnet tests on self-hosted for Mercurial 6 on develop: backend/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L167
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.
Integration tests / Dotnet tests on self-hosted for Mercurial 6 on develop
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 / Dotnet tests on self-hosted for Mercurial 6 on develop: backend/LfClassicData/LfClassicLexboxApi.cs#L191
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.
Integration tests / Dotnet tests on self-hosted for Mercurial 6 on develop: backend/LexBoxApi/Auth/JwtTicketDataFormat.cs#L122
'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 / Dotnet tests on self-hosted for Mercurial 6 on develop: backend/LexBoxApi/Services/HgService.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 '(LexBoxApi.Services.RepoEmptyState)2' is not covered.
Integration tests / Dotnet tests on self-hosted for Mercurial 6 on develop: backend/LexBoxApi/GraphQL/CustomTypes/IsLanguageForgeProjectDataLoader.cs#L27
Method referencing lambda parameter is not supported LINQ expression. (https://www.mongodb.com/docs/mongodb-analyzer/current/rules/#MALinq2001)
Integration tests / Dotnet tests on self-hosted for Mercurial 6 on develop: backend/FwLite/LcmCrdt/LcmCrdtKernel.cs#L4
The using directive for 'Crdt' appeared previously in this namespace