Skip to content

Begin moving to Semantic Kernel & integrating FiveM server #11

Begin moving to Semantic Kernel & integrating FiveM server

Begin moving to Semantic Kernel & integrating FiveM server #11

Triggered via pull request May 17, 2024 23:33
@MickMelonMickMelon
synchronize #6
rewrite
Status Success
Total duration 26s
Artifacts

dotnet.yml

on: pull_request
build-dotnet-core
18s
build-dotnet-core
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
build-dotnet-core
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-dotnet-core: src/IntelliPed.Core/Agents/Agent.cs#L51
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-dotnet-core: src/IntelliPed.Core/Agents/Agent.cs#L59
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-dotnet-core: src/IntelliPed.Core/Agents/Agent.cs#L51
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-dotnet-core: src/IntelliPed.Core/Agents/Agent.cs#L59
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.