Skip to content

fix queue names for Notifications #90

fix queue names for Notifications

fix queue names for Notifications #90

Triggered via push November 25, 2024 16:23
Status Success
Total duration 34s
Artifacts

dotnet.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build: Arbitrer.RabbitMQ/RequestsManager.cs#L272
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: Arbitrer.RabbitMQ/RequestsManager.cs#L272
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: Arbitrer.RabbitMQ/RequestsManager.cs#L272
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: Arbitrer.RabbitMQ/RequestsManager.cs#L272
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.