Skip to content

setup FW Lite as a maui app #87

setup FW Lite as a maui app

setup FW Lite as a maui app #87

Triggered via pull request July 24, 2024 04:24
Status Failure
Total duration 27m 59s
Artifacts 2

fw-lite.yaml

on: pull_request
Build FW Lite and run tests
7m 22s
Build FW Lite and run tests
Publish FW Lite app
20m 10s
Publish FW Lite app
Sign FWLite MSIX installer
0s
Sign FWLite MSIX installer
Create Release
0s
Create Release
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 58 warnings
Publish FW Lite app
The job running on runner GitHub Actions 3 has exceeded the maximum execution time of 20 minutes.
Publish FW Lite app
The operation was canceled.
Build FW Lite and run tests: backend/FwLite/MiniLcm/InMemoryApi.cs#L177
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#L182
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#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 FW Lite and run tests: backend/FwLite/MiniLcm/InMemoryApi.cs#L233
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/Api/FwDataMiniLcmApi.cs#L152
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/Api/FwDataMiniLcmApi.cs#L160
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/Api/FwDataMiniLcmApi.cs#L165
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/Api/FwDataMiniLcmApi.cs#L178
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/Api/FwDataMiniLcmApi.cs#L250
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
Publish FW Lite app: backend/FwLite/MiniLcm/InMemoryApi.cs#L177
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.
Publish FW Lite app: backend/FwLite/MiniLcm/InMemoryApi.cs#L182
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.
Publish FW Lite app: 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.
Publish FW Lite app: backend/FwLite/MiniLcm/InMemoryApi.cs#L233
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.
Publish FW Lite app: backend/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L152
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.
Publish FW Lite app: backend/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L160
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.
Publish FW Lite app: backend/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L165
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.
Publish FW Lite app: backend/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L178
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.
Publish FW Lite app: backend/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L250
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.
Publish FW Lite app: backend/FwLite/FwDataMiniLcmBridge/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
Publish FW Lite app: backend/FwLite/LocalWebApp/SyncService.cs#L10
Parameter 'factory' is unread.
Publish FW Lite app: backend/FwLite/LocalWebApp/BackgroundSyncService.cs#L11
Parameter 'serviceProvider' is unread.
Publish FW Lite app: backend/FwLite/LocalWebApp/CrdtHttpSyncService.cs#L64
Parameter 'originDomain' is unread.
Publish FW Lite app: backend/FwLite/LocalWebApp/Routes/HistoryRoutes.cs#L45
The result of the expression is always 'true' since a value of type 'Guid' is never equal to 'null' of type 'Guid?'
Publish FW Lite app: backend/FwLite/LocalWebApp/Routes/HistoryRoutes.cs#L45
The result of the expression is always 'true' since a value of type 'Guid' is never equal to 'null' of type 'Guid?'
Publish FW Lite app: backend/FwLite/FwLiteDesktop/ServerBridge/ServerManager.cs#L39
Synchronously waiting on tasks or awaiters may cause deadlocks. Use await or JoinableTaskFactory.Run instead. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD002.md)
Publish FW Lite app: backend/FwLite/FwLiteDesktop/ServerBridge/ServerManager.cs#L47
Synchronously waiting on tasks or awaiters may cause deadlocks. Use await or JoinableTaskFactory.Run instead. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD002.md)
Publish FW Lite app: backend/FwLite/FwLiteDesktop/ServerBridge/ServerManager.cs#L48
Synchronously waiting on tasks or awaiters may cause deadlocks. Use await or JoinableTaskFactory.Run instead. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD002.md)
Publish FW Lite app: backend/FwLite/LocalWebApp/SyncService.cs#L10
Parameter 'factory' is unread.
Publish FW Lite app: backend/FwLite/LocalWebApp/BackgroundSyncService.cs#L11
Parameter 'serviceProvider' is unread.
Publish FW Lite app: backend/FwLite/LocalWebApp/CrdtHttpSyncService.cs#L64
Parameter 'originDomain' is unread.
Publish FW Lite app: backend/FwLite/LocalWebApp/Routes/HistoryRoutes.cs#L45
The result of the expression is always 'true' since a value of type 'Guid' is never equal to 'null' of type 'Guid?'
Publish FW Lite app: backend/FwLite/LocalWebApp/Routes/HistoryRoutes.cs#L45
The result of the expression is always 'true' since a value of type 'Guid' is never equal to 'null' of type 'Guid?'
Publish FW Lite app: backend/FwLite/LocalWebApp/SyncService.cs#L10
Parameter 'factory' is unread.
Publish FW Lite app: backend/FwLite/LocalWebApp/BackgroundSyncService.cs#L11
Parameter 'serviceProvider' is unread.
Publish FW Lite app: backend/FwLite/LocalWebApp/CrdtHttpSyncService.cs#L64
Parameter 'originDomain' is unread.
Publish FW Lite app: backend/FwLite/LocalWebApp/Routes/HistoryRoutes.cs#L45
The result of the expression is always 'true' since a value of type 'Guid' is never equal to 'null' of type 'Guid?'
Publish FW Lite app: backend/FwLite/LocalWebApp/Routes/HistoryRoutes.cs#L45
The result of the expression is always 'true' since a value of type 'Guid' is never equal to 'null' of type 'Guid?'
Publish FW Lite app: backend/FwLite/FwLiteDesktop/ServerBridge/ServerManager.cs#L39
Synchronously waiting on tasks or awaiters may cause deadlocks. Use await or JoinableTaskFactory.Run instead. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD002.md)
Publish FW Lite app: backend/FwLite/FwLiteDesktop/ServerBridge/ServerManager.cs#L47
Synchronously waiting on tasks or awaiters may cause deadlocks. Use await or JoinableTaskFactory.Run instead. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD002.md)
Publish FW Lite app: backend/FwLite/FwLiteDesktop/ServerBridge/ServerManager.cs#L48
Synchronously waiting on tasks or awaiters may cause deadlocks. Use await or JoinableTaskFactory.Run instead. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD002.md)
Publish FW Lite app: backend/FwLite/LocalWebApp/SyncService.cs#L10
Parameter 'factory' is unread.
Publish FW Lite app: backend/FwLite/LocalWebApp/CrdtHttpSyncService.cs#L64
Parameter 'originDomain' is unread.
Publish FW Lite app: backend/FwLite/LocalWebApp/BackgroundSyncService.cs#L11
Parameter 'serviceProvider' is unread.
Publish FW Lite app: backend/FwLite/LocalWebApp/Routes/HistoryRoutes.cs#L45
The result of the expression is always 'true' since a value of type 'Guid' is never equal to 'null' of type 'Guid?'
Publish FW Lite app: backend/FwLite/LocalWebApp/Routes/HistoryRoutes.cs#L45
The result of the expression is always 'true' since a value of type 'Guid' is never equal to 'null' of type 'Guid?'
Publish FW Lite app: backend/FwLite/LocalWebApp/SyncService.cs#L10
Parameter 'factory' is unread.
Publish FW Lite app: backend/FwLite/LocalWebApp/BackgroundSyncService.cs#L11
Parameter 'serviceProvider' is unread.
Publish FW Lite app: backend/FwLite/LocalWebApp/CrdtHttpSyncService.cs#L64
Parameter 'originDomain' is unread.
Publish FW Lite app: backend/FwLite/LocalWebApp/Routes/HistoryRoutes.cs#L45
The result of the expression is always 'true' since a value of type 'Guid' is never equal to 'null' of type 'Guid?'
Publish FW Lite app: backend/FwLite/LocalWebApp/Routes/HistoryRoutes.cs#L45
The result of the expression is always 'true' since a value of type 'Guid' is never equal to 'null' of type 'Guid?'

Artifacts

Produced during runtime
Name Size
fw-lite-local-web-app Expired
315 MB
fw-lite-unpackaged Expired
266 MB