Update to dotnet 8 #28
TRybina132Annotations
12 warnings
|
build-and-test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1, b3b00/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build-and-test:
ManagedCode.Queue.Core/InMemoryQueue.cs#L23
Async-iterator 'InMemoryQueue.ReceiveMessages(string, string, CancellationToken)' has one or more parameters of type 'CancellationToken' but none of them is decorated with the 'EnumeratorCancellation' attribute, so the cancellation token parameter from the generated 'IAsyncEnumerable<>.GetAsyncEnumerator' will be unconsumed
|
|
build-and-test:
ManagedCode.Queue.Core/InMemoryQueue.cs#L40
Async-iterator 'InMemoryQueue.ReceiveMessages(string, CancellationToken)' has one or more parameters of type 'CancellationToken' but none of them is decorated with the 'EnumeratorCancellation' attribute, so the cancellation token parameter from the generated 'IAsyncEnumerable<>.GetAsyncEnumerator' will be unconsumed
|
|
build-and-test:
ManagedCode.Queue.Core/Abstractions/IQueueSender.cs#L14
The EnumeratorCancellationAttribute applied to parameter 'cancellationToken' will have no effect. The attribute is only effective on a parameter of type CancellationToken in an async-iterator method returning IAsyncEnumerable
|
|
build-and-test:
ManagedCode.Queue.Core/Abstractions/IQueueSender.cs#L15
The EnumeratorCancellationAttribute applied to parameter 'cancellationToken' will have no effect. The attribute is only effective on a parameter of type CancellationToken in an async-iterator method returning IAsyncEnumerable
|
|
build-and-test:
ManagedCode.Queue.Core/Models/Message.cs#L7
Non-nullable property 'Id' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-and-test:
ManagedCode.Queue.Core/Models/Message.cs#L12
Non-nullable property 'Body' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-and-test:
ManagedCode.Queue.AzureServiceBus/AzureServiceBusReceiver.cs#L71
Async-iterator 'AzureServiceBusQueue.ReceiveMessages(string, string, CancellationToken)' has one or more parameters of type 'CancellationToken' but none of them is decorated with the 'EnumeratorCancellation' attribute, so the cancellation token parameter from the generated 'IAsyncEnumerable<>.GetAsyncEnumerator' will be unconsumed
|
|
build-and-test:
ManagedCode.Queue.AzureServiceBus/AzureServiceBusReceiver.cs#L95
Async-iterator 'AzureServiceBusQueue.ReceiveMessages(string, CancellationToken)' has one or more parameters of type 'CancellationToken' but none of them is decorated with the 'EnumeratorCancellation' attribute, so the cancellation token parameter from the generated 'IAsyncEnumerable<>.GetAsyncEnumerator' will be unconsumed
|
|
build-and-test:
ManagedCode.Queue.AzureServiceBus/Options/AzureServiceBusOptions.cs#L7
Non-nullable property 'ConnectionString' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-and-test:
ManagedCode.Queue.AzureServiceBus/Options/AzureServiceBusOptions.cs#L8
Non-nullable property 'FullyQualifiedNamespace' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-and-test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|