Skip to content

Merge pull request #13 from atomsk-0/controllerSupport #49

Merge pull request #13 from atomsk-0/controllerSupport

Merge pull request #13 from atomsk-0/controllerSupport #49

Triggered via push March 4, 2025 13:38
Status Success
Total duration 1m 41s
Artifacts 2
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

20 warnings
build (Release)
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.
build (Release): Settings/InstalledPackages.cs#L76
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build (Release): Settings/InstalledPackages.cs#L81
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build (Release): Dialogs/ProgressController.cs#L47
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 (Release): Dialogs/ProgressController.cs#L43
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 (Release): Dialogs/ProgressController.cs#L62
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 (Release): Dialogs/ProgressController.cs#L58
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 (Release): Pages/Settings/UiSettingsPage.xaml.cs#L56
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 (Release): Pages/Settings/UiSettingsPage.xaml.cs#L77
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 (Release): Utils/Packages.cs#L215
Converting null literal or possible null value to non-nullable type.
build (Debug)
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.
build (Debug): Settings/InstalledPackages.cs#L76
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build (Debug): Settings/InstalledPackages.cs#L81
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build (Debug): Dialogs/ProgressController.cs#L47
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 (Debug): Dialogs/ProgressController.cs#L43
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 (Debug): Dialogs/ProgressController.cs#L62
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 (Debug): Dialogs/ProgressController.cs#L58
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 (Debug): Pages/Settings/UiSettingsPage.xaml.cs#L56
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 (Debug): Pages/Settings/UiSettingsPage.xaml.cs#L77
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 (Debug): Pages/AppsListPage.xaml.cs#L322
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.

Artifacts

Produced during runtime
Name Size Digest
WinDurangoUI-Debug Expired
30.9 MB
sha256:deef51dc9fa832f1d55ac12cc812a72cc55d8ee0f6db2d63d95e4ceb6f3576aa
WinDurangoUI-Release Expired
30.9 MB
sha256:d754c5be1e53576800d876fb99787de9d8435b85e4ba3ff5ca58ff5ce753a682