mini lcm refactor #175
Triggered via pull request
September 24, 2024 08:56
hahn-kev
Status
Failure
Total duration
3m 58s
Artifacts
–
fw-lite.yaml
on: pull_request
Build FW Lite and run tests
3m 40s
Publish FW Lite app for Mac
0s
Publish FW Lite app for Linux
0s
Create Release
0s
Annotations
3 errors and 10 warnings
|
Build FW Lite and run tests:
backend/FwLite/LocalWebApp/Routes/TestRoutes.cs#L28
The type or namespace name 'ILexboxApi' could not be found (are you missing a using directive or an assembly reference?)
|
|
Build FW Lite and run tests:
backend/FwLite/LocalWebApp/Routes/TestRoutes.cs#L28
The type or namespace name 'ILexboxApi' could not be found (are you missing a using directive or an assembly reference?)
|
|
Build FW Lite and run tests
Process completed with exit code 1.
|
|
Build FW Lite and run tests:
backend/FwLite/MiniLcm/InMemoryApi.cs#L179
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 FW Lite and run tests:
backend/FwLite/MiniLcm/InMemoryApi.cs#L184
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 FW Lite and run tests:
backend/FwLite/MiniLcm/InMemoryApi.cs#L216
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 FW Lite and run tests:
backend/FwLite/MiniLcm/InMemoryApi.cs#L235
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 FW Lite and run tests:
backend/FwLite/FwDataMiniLcmBridge/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
|
|
Build FW Lite and run tests:
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 FW Lite and run tests:
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 FW Lite and run tests:
backend/FwLite/LcmCrdt/LcmCrdtKernel.cs#L4
The using directive for 'SIL.Harmony' appeared previously in this namespace
|
|
Build FW Lite and run tests:
backend/FwLite/LcmCrdt/CrdtMiniLcmApi.cs#L15
Parameter 'timeProvider' is unread.
|
|
Build FW Lite and run tests:
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.
|