[ISSUE #776] Add push consumer for normal/fifo message, namespace support, reentrant message receiving support in C# SDK #1307
Annotations
9 warnings
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Build artifacts:
csharp/tests/ClientTest.cs#L36
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 artifacts:
csharp/tests/ClientTest.cs#L100
The variable 'e' is declared but never used
|
|
Build artifacts:
csharp/tests/ClientTest.cs#L107
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 artifacts:
csharp/tests/ProcessQueueTest.cs#L112
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 artifacts:
csharp/tests/ClientTest.cs#L36
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 artifacts:
csharp/tests/ClientTest.cs#L100
The variable 'e' is declared but never used
|
|
Build artifacts:
csharp/tests/ClientTest.cs#L107
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 artifacts:
csharp/tests/ProcessQueueTest.cs#L112
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.
|
Loading