Skip to content

CRDT sync handles semantic domains #63

CRDT sync handles semantic domains

CRDT sync handles semantic domains #63

Triggered via pull request November 11, 2024 02:49
Status Failure
Total duration 1m 47s
Artifacts

develop-fw-headless.yaml

on: pull_request
Set Version
0s
Set Version
Build FwHeadless  /  publish-fw-headless
1m 26s
Build FwHeadless / publish-fw-headless
Deploy FwHeadless  /  deploy
Deploy FwHeadless / deploy
Matrix: Deploy FwHeadless / verify-published
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 10 warnings
Build FwHeadless / publish-fw-headless
Duplicate 'Content' items were included. The .NET SDK includes 'Content' items from your project directory by default. You can either remove these items from your project file, or set the 'EnableDefaultContentItems' property to 'false' if you want to explicitly include them in your project file. For more information, see https://aka.ms/sdkimplicititems. The duplicate items were: 'Mercurial/contrib/asv.conf.json'
Build FwHeadless / publish-fw-headless
Duplicate 'Content' items were included. The .NET SDK includes 'Content' items from your project directory by default. You can either remove these items from your project file, or set the 'EnableDefaultContentItems' property to 'false' if you want to explicitly include them in your project file. For more information, see https://aka.ms/sdkimplicititems. The duplicate items were: 'Mercurial/contrib/asv.conf.json'
Build FwHeadless / publish-fw-headless
Duplicate 'Content' items were included. The .NET SDK includes 'Content' items from your project directory by default. You can either remove these items from your project file, or set the 'EnableDefaultContentItems' property to 'false' if you want to explicitly include them in your project file. For more information, see https://aka.ms/sdkimplicititems. The duplicate items were: 'Mercurial/contrib/asv.conf.json'
Build FwHeadless / publish-fw-headless
buildx failed with: ERROR: failed to solve: process "/bin/sh -c dotnet build /p:InformationalVersion=$APP_VERSION \"FwHeadless/FwHeadless.csproj\" -c Release -o /app/build" did not complete successfully: exit code: 1
Build FwHeadless / publish-fw-headless: backend/FwLite/FwDataMiniLcmBridge/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
Build FwHeadless / publish-fw-headless: backend/FwLite/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateSenseProxy.cs#L121
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 FwHeadless / publish-fw-headless: backend/FwLite/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateEntryProxy.cs#L53
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 FwHeadless / publish-fw-headless: 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.
Build FwHeadless / publish-fw-headless: backend/FwLite/LcmCrdt/CrdtMiniLcmApi.cs#L308
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 FwHeadless / publish-fw-headless: backend/FwLite/FwLiteProjectSync/DryRunMiniLcmApi.cs#L30
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 '(MiniLcm.Models.WritingSystemType)2' is not covered.
Build FwHeadless / publish-fw-headless: backend/FwLite/FwDataMiniLcmBridge/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used