Add support of net9 on github actions #142
arnaudleclerc
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
Annotations
15 warnings
|
build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build:
tests/AzureMapsControl.Components.Tests/Traffic/TrafficOptions.cs#L48
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:
tests/AzureMapsControl.Components.Tests/Traffic/TrafficOptions.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:
tests/AzureMapsControl.Components.Tests/Drawing/DrawingToolbarEventInvokeHelper.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.
|
|
build:
tests/AzureMapsControl.Components.Tests/Markers/HtmlMarkerInvokeHelper.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.
|
|
build:
tests/AzureMapsControl.Components.Tests/Map/MapService.cs#L28
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:
tests/AzureMapsControl.Components.Tests/Map/MapEventInvokeHelper.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.
|
|
build:
tests/AzureMapsControl.Components.Tests/Layers/LayerEventInvokeHelper.cs#L17
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:
tests/AzureMapsControl.Components.Tests/Traffic/TrafficOptions.cs#L48
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:
tests/AzureMapsControl.Components.Tests/Traffic/TrafficOptions.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:
tests/AzureMapsControl.Components.Tests/Drawing/DrawingToolbarEventInvokeHelper.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.
|
|
build:
src/AzureMapsControl.Components/Map/AzureMap.razor#L58
Component parameter 'AzureMapsControl.Components.Map.AzureMap.Id' should be auto property
|
|
build:
src/AzureMapsControl.Components/Map/AzureMap.razor#L58
Component parameter 'AzureMapsControl.Components.Map.AzureMap.Id' should be auto property
|
|
build:
src/AzureMapsControl.Components/Map/AzureMap.razor#L58
Component parameter 'AzureMapsControl.Components.Map.AzureMap.Id' should be auto property
|
|
build:
src/AzureMapsControl.Components/Map/AzureMap.razor#L58
Component parameter 'AzureMapsControl.Components.Map.AzureMap.Id' should be auto property
|