Merge pull request #4167 from BrighterCommand/dependabot/nuget/Aspire… #7738
iancooperci.yml
on: push
build
8m 20s
release
0s
memory
3m 4s
hangfire
3m 45s
quartz
3m 40s
tickerq
4m 5s
redis-ci
1m 49s
mqtt-ci
1m 36s
rabbitmq-ci
5m 11s
kafka-ci
7m 59s
postgres-ci
2m 18s
sqlserver-ci
2m 8s
mysql-ci
2m 5s
dynamo-ci
2m 29s
aws-mock-ci
4m 41s
aws-ci
4m 11s
aws-scheduler-ci
1m 41s
sqlite-ci
2m 0s
azure-ci
1m 47s
mongodb-ci
2m 20s
gcp-ci
3m 30s
Annotations
7 errors and 204 warnings
|
azure-ci
Process completed with exit code 1.
|
|
Paramore.Brighter.AzureServiceBus.Tests.MessagingGateway.ASBConsumerTests.When_requeueing_a_message_via_the_consumer:
tests/Paramore.Brighter.AzureServiceBus.Tests/MessagingGateway/When_consuming_a_message_via_the_consumer.cs#L193
System.ArgumentException : An item with the same key has already been added. Key: SequenceNumber
|
|
Paramore.Brighter.AzureServiceBus.Tests.MessagingGateway.ASBConsumerTests.When_requeueing_a_message_via_the_consumer:
tests/Paramore.Brighter.AzureServiceBus.Tests/MessagingGateway/When_consuming_a_message_via_the_consumer.cs#L193
System.ArgumentException : An item with the same key has already been added. Key: SequenceNumber
|
|
gcp-ci
Process completed with exit code 1.
|
|
Paramore.Brighter.Gcp.Tests.MessagingGateway.Pull.Reactor.MessageProducerDlqTestsAsync.When_requeueing_redrives_to_the_queue:
tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Reactor/When_requeueing_redrives_to_the_dlq.cs#L84
Assert.Equal() Failure: Values differ
Expected: 1
Actual: 0
|
|
aws-ci
Process completed with exit code 1.
|
|
Paramore.Brighter.AWS.Tests.MessagingGateway.Sns.Standard.Reactor.SqsMessageProducerSendTests.When_posting_a_message_via_the_producer:
tests/Paramore.Brighter.AWS.Tests/MessagingGateway/Sns/Standard/Reactor/When_posting_a_message_via_the_messaging_gateway.cs#L80
Assert.Equal() Failure: Values differ
Expected: MT_COMMAND
Actual: MT_NONE
|
|
build
ClaimCheckAttribute should be applied 'MapToMessage' Method
|
|
build
CompressAttribute should be applied 'MapToMessage' Method
|
|
build
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
azure-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
azure-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
azure-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
azure-ci
The variable 'tryMessage2CallBack' is assigned but its value is never used
|
|
azure-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
azure-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
azure-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
azure-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
azure-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
azure-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlserver-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlserver-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlserver-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlserver-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlserver-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlserver-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlserver-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlserver-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlserver-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlserver-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
quartz
'CommandProcessor.CIRCUITBREAKERASYNC' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
quartz
'CommandProcessor.RETRYPOLICYASYNC' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
quartz
'CommandProcessor.CIRCUITBREAKER' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
quartz
'CommandProcessor.RETRYPOLICY' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
quartz
'CommandProcessor.CIRCUITBREAKERASYNC' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
quartz
'CommandProcessor.RETRYPOLICYASYNC' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
quartz
'CommandProcessor.CIRCUITBREAKER' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
quartz
'CommandProcessor.RETRYPOLICY' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
quartz
'CommandProcessor.CIRCUITBREAKERASYNC' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
quartz
'CommandProcessor.RETRYPOLICYASYNC' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
sqlite-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlite-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlite-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlite-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlite-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlite-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlite-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlite-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlite-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
sqlite-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mysql-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mysql-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mysql-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mysql-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mysql-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mysql-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mysql-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mysql-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mysql-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mysql-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-scheduler-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-scheduler-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-scheduler-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-scheduler-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-scheduler-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-scheduler-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-scheduler-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-scheduler-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-scheduler-ci
'MessageBody.Bytes' is obsolete: 'Use Memory for zero-copy access. This property allocates on every call.'
|
|
aws-scheduler-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mqtt-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mqtt-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mqtt-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mqtt-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mqtt-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mqtt-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mqtt-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mqtt-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mqtt-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mqtt-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
memory
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
|
|
memory
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
memory
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
memory
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
memory
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
memory
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
memory
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
memory
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
memory
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
memory
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
postgres-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
postgres-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
postgres-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
postgres-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
postgres-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
postgres-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
postgres-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
postgres-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
postgres-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
postgres-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
redis-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
redis-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
redis-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
redis-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
redis-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
redis-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
redis-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
redis-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
redis-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
redis-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
gcp-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
gcp-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
gcp-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
gcp-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
gcp-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
gcp-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
gcp-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
gcp-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
gcp-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
gcp-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
rabbitmq-ci
Type 'StubMessageScheduler' can be sealed because it has no subtypes in its containing assembly and is not externally visible (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1852)
|
|
rabbitmq-ci
Do not use Assert.Equal() to check for collection size. Use Assert.Single instead. (https://xunit.net/xunit.analyzers/rules/xUnit2013)
|
|
rabbitmq-ci
Do not use Assert.Equal() to check for boolean conditions. Use Assert.True instead. (https://xunit.net/xunit.analyzers/rules/xUnit2004)
|
|
rabbitmq-ci
The field 'RmqMessageConsumerConnectionClosedTests._firstException' is never used
|
|
rabbitmq-ci
The variable 'cfe' is declared but never used
|
|
rabbitmq-ci
'CommandProcessor.CIRCUITBREAKER' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
rabbitmq-ci
'CommandProcessor.RETRYPOLICY' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
rabbitmq-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
rabbitmq-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
rabbitmq-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
rabbitmq-ci
'CommandProcessor.CIRCUITBREAKER' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
rabbitmq-ci
'CommandProcessor.RETRYPOLICY' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
rabbitmq-ci
'CommandProcessor.CIRCUITBREAKER' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
rabbitmq-ci
'CommandProcessor.RETRYPOLICY' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
rabbitmq-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
rabbitmq-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
rabbitmq-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
rabbitmq-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
rabbitmq-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
rabbitmq-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mongodb-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mongodb-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mongodb-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mongodb-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mongodb-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mongodb-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mongodb-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mongodb-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mongodb-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
mongodb-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
dynamo-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
dynamo-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
dynamo-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
dynamo-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
dynamo-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
dynamo-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
dynamo-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
dynamo-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
dynamo-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
dynamo-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-mock-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-mock-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-mock-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-mock-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-mock-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-mock-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-mock-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-mock-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-mock-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
aws-mock-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
hangfire
'CommandProcessor.CIRCUITBREAKER' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
hangfire
'CommandProcessor.RETRYPOLICY' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
hangfire
'CommandProcessor.CIRCUITBREAKER' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
hangfire
'CommandProcessor.RETRYPOLICY' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
hangfire
'CommandProcessor.CIRCUITBREAKERASYNC' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
hangfire
'CommandProcessor.RETRYPOLICYASYNC' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
hangfire
'CommandProcessor.CIRCUITBREAKERASYNC' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
hangfire
'CommandProcessor.RETRYPOLICYASYNC' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
hangfire
'CommandProcessor.CIRCUITBREAKER' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
hangfire
'CommandProcessor.RETRYPOLICY' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
tickerq
'CommandProcessor.CIRCUITBREAKER' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
tickerq
'CommandProcessor.RETRYPOLICY' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
tickerq
'CommandProcessor.CIRCUITBREAKER' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
tickerq
'CommandProcessor.RETRYPOLICY' is obsolete: 'Migrate to Resilience Pipeline with OutboxProducer'
|
|
kafka-ci
'MessageBody.Bytes' is obsolete: 'Use Memory for zero-copy access. This property allocates on every call.'
|
|
kafka-ci
'MessageBody.Bytes' is obsolete: 'Use Memory for zero-copy access. This property allocates on every call.'
|
|
kafka-ci
'MessageBody.Bytes' is obsolete: 'Use Memory for zero-copy access. This property allocates on every call.'
|
|
kafka-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
kafka-ci
'MessageBody.Bytes' is obsolete: 'Use Memory for zero-copy access. This property allocates on every call.'
|
|
kafka-ci
'MessageBody.Bytes' is obsolete: 'Use Memory for zero-copy access. This property allocates on every call.'
|
|
kafka-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
kafka-ci
'MessageBody.Bytes' is obsolete: 'Use Memory for zero-copy access. This property allocates on every call.'
|
|
kafka-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
kafka-ci
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
nuget packages
|
19 MB |
sha256:13ad02a1b9c584fc8653fef7abcb3edd1c4185641992ab906a526a0d16683881
|
|