Database Utilities for our boxes #7651
iancooperci.yml
on: pull_request
build
6m 51s
release
0s
memory
3m 13s
hangfire
3m 45s
quartz
3m 45s
tickerq
4m 12s
redis-ci
2m 2s
mqtt-ci
1m 40s
rabbitmq-ci
5m 14s
kafka-ci
7m 22s
postgres-ci
2m 4s
sqlserver-ci
2m 1s
mysql-ci
1m 56s
dynamo-ci
2m 22s
aws-mock-ci
4m 34s
aws-ci
6m 53s
aws-scheduler-ci
1m 30s
sqlite-ci
1m 31s
azure-ci
1m 56s
mongodb-ci
2m 38s
gcp-ci
2m 49s
Annotations
12 errors and 204 warnings
|
postgres-ci
Process completed with exit code 1.
|
|
Paramore.Brighter.PostgresSQL.Tests.BoxProvisioning.When_many_postgres_provisioners_race_to_create_history_table_they_should_all_complete.Should_all_complete_without_transaction_abort:
tests/Paramore.Brighter.PostgresSQL.Tests/BoxProvisioning/When_many_postgres_provisioners_race_to_create_history_table_they_should_all_complete.cs#L109
Expected at least one 'history_table_race_swallowed' event across 16 racers; got none. The race window did not fire.
|
|
Paramore.Brighter.Gcp.Tests.Spanner.BoxProvisioning.SpannerOutboxFreshInstallTests.Should_stamp_v_latest_with_fresh_install_description_and_skip_duplicate_on_rerun:
tests/Paramore.Brighter.Gcp.Tests/Spanner/BoxProvisioning/When_spanner_fresh_install_runs_it_should_create_table_and_stamp_v_latest_and_skip_duplicate_history_insert.cs#L56
Google.Cloud.Spanner.Data.SpannerException : Insufficient permission to execute the specified operation.
---- Grpc.Core.RpcException : Status(StatusCode="PermissionDenied", Detail="Operation denied by [IAM permission 'spanner.sessions.create' on resource '//spanner.googleapis.com/projects/brighter-464321/instances/brighter-spanner/databases/brightertests'].")
|
|
Paramore.Brighter.Gcp.Tests.Spanner.BoxProvisioning.SpannerInboxFreshInstallTests.Should_stamp_v_latest_with_fresh_install_description_and_skip_duplicate_on_rerun:
tests/Paramore.Brighter.Gcp.Tests/Spanner/BoxProvisioning/When_spanner_fresh_install_runs_it_should_create_table_and_stamp_v_latest_and_skip_duplicate_history_insert.cs#L150
Google.Cloud.Spanner.Data.SpannerException : Insufficient permission to execute the specified operation.
---- Grpc.Core.RpcException : Status(StatusCode="PermissionDenied", Detail="Operation denied by [IAM permission 'spanner.sessions.create' on resource '//spanner.googleapis.com/projects/brighter-464321/instances/brighter-spanner/databases/brightertests'].")
|
|
Paramore.Brighter.Gcp.Tests.Spanner.BoxProvisioning.When_spanner_inbox_provisioner_finds_existing_table_without_history_it_should_bootstrap.Should_bootstrap_with_synthetic_history:
tests/Paramore.Brighter.Gcp.Tests/Spanner/BoxProvisioning/When_spanner_inbox_provisioner_finds_existing_table_without_history_it_should_bootstrap.cs#L39
Google.Cloud.Spanner.Data.SpannerException : Insufficient permission to execute the specified operation.
---- Grpc.Core.RpcException : Status(StatusCode="PermissionDenied", Detail="Operation denied by [IAM permission 'spanner.databases.updateDdl' on resource '//spanner.googleapis.com/projects/brighter-464321/instances/brighter-spanner/databases/brightertests'].")
|
|
Paramore.Brighter.Gcp.Tests.Spanner.BoxProvisioning.InboxProvisionerFreshDatabaseTests.Should_create_inbox_table:
tests/Paramore.Brighter.Gcp.Tests/Spanner/BoxProvisioning/When_spanner_inbox_provisioner_runs_on_fresh_database_it_should_create_inbox_table.cs#L34
Google.Cloud.Spanner.Data.SpannerException : Insufficient permission to execute the specified operation.
---- Grpc.Core.RpcException : Status(StatusCode="PermissionDenied", Detail="Operation denied by [IAM permission 'spanner.sessions.create' on resource '//spanner.googleapis.com/projects/brighter-464321/instances/brighter-spanner/databases/brightertests'].")
|
|
Paramore.Brighter.Gcp.Tests.Spanner.BoxProvisioning.When_spanner_outbox_provisioner_finds_existing_table_without_history_it_should_bootstrap.Should_bootstrap_with_synthetic_history:
tests/Paramore.Brighter.Gcp.Tests/Spanner/BoxProvisioning/When_spanner_outbox_provisioner_finds_existing_table_without_history_it_should_bootstrap.cs#L39
Google.Cloud.Spanner.Data.SpannerException : Insufficient permission to execute the specified operation.
---- Grpc.Core.RpcException : Status(StatusCode="PermissionDenied", Detail="Operation denied by [IAM permission 'spanner.databases.updateDdl' on resource '//spanner.googleapis.com/projects/brighter-464321/instances/brighter-spanner/databases/brightertests'].")
|
|
Paramore.Brighter.Gcp.Tests.Spanner.BoxProvisioning.OutboxProvisionerFreshDatabaseTests.Should_create_outbox_table:
tests/Paramore.Brighter.Gcp.Tests/Spanner/BoxProvisioning/When_spanner_outbox_provisioner_runs_on_fresh_database_it_should_create_outbox_table.cs#L34
Google.Cloud.Spanner.Data.SpannerException : Insufficient permission to execute the specified operation.
---- Grpc.Core.RpcException : Status(StatusCode="PermissionDenied", Detail="Operation denied by [IAM permission 'spanner.sessions.create' on resource '//spanner.googleapis.com/projects/brighter-464321/instances/brighter-spanner/databases/brightertests'].")
|
|
Paramore.Brighter.Gcp.Tests.Spanner.BoxProvisioning.When_spanner_provisioner_runs_against_existing_outbox_with_mismatched_payload_mode_it_should_throw_configuration_exception.Should_throw_when_existing_outbox_body_is_string_and_provisioner_is_configured_for_binary:
tests/Paramore.Brighter.Gcp.Tests/Spanner/BoxProvisioning/When_spanner_provisioner_runs_against_existing_outbox_with_mismatched_payload_mode_it_should_throw_configuration_exception.cs#L45
Google.Cloud.Spanner.Data.SpannerException : Insufficient permission to execute the specified operation.
---- Grpc.Core.RpcException : Status(StatusCode="PermissionDenied", Detail="Operation denied by [IAM permission 'spanner.databases.updateDdl' on resource '//spanner.googleapis.com/projects/brighter-464321/instances/brighter-spanner/databases/brightertests'].")
|
|
Paramore.Brighter.Gcp.Tests.Spanner.BoxProvisioning.When_spanner_provisioner_runs_against_existing_outbox_with_mismatched_payload_mode_it_should_throw_configuration_exception.Should_throw_when_existing_outbox_body_is_bytes_and_provisioner_is_configured_for_text:
tests/Paramore.Brighter.Gcp.Tests/Spanner/BoxProvisioning/When_spanner_provisioner_runs_against_existing_outbox_with_mismatched_payload_mode_it_should_throw_configuration_exception.cs#L62
Google.Cloud.Spanner.Data.SpannerException : Insufficient permission to execute the specified operation.
---- Grpc.Core.RpcException : Status(StatusCode="PermissionDenied", Detail="Operation denied by [IAM permission 'spanner.databases.updateDdl' on resource '//spanner.googleapis.com/projects/brighter-464321/instances/brighter-spanner/databases/brightertests'].")
|
|
Paramore.Brighter.Gcp.Tests.Spanner.BoxProvisioning.SpannerConcurrentBootstrapTests.Should_not_throw_when_two_concurrent_bootstrap_callers_race_on_history_insert:
tests/Paramore.Brighter.Gcp.Tests/Spanner/BoxProvisioning/When_spanner_runner_runs_two_concurrent_bootstrap_callers_against_an_existing_table_neither_should_throw.cs#L69
Google.Cloud.Spanner.Data.SpannerException : Insufficient permission to execute the specified operation.
---- Grpc.Core.RpcException : Status(StatusCode="PermissionDenied", Detail="Operation denied by [IAM permission 'spanner.databases.updateDdl' on resource '//spanner.googleapis.com/projects/brighter-464321/instances/brighter-spanner/databases/brightertests'].")
|
|
Paramore.Brighter.Gcp.Tests.Spanner.BoxProvisioning.SpannerConcurrentFreshInstallTests.Should_not_throw_when_two_concurrent_fresh_installers_race_on_history_insert:
tests/Paramore.Brighter.Gcp.Tests/Spanner/BoxProvisioning/When_spanner_runner_runs_two_concurrent_fresh_installers_neither_should_throw.cs#L72
Assert.Null() Failure: Value is not null
Expected: null
Actual: Google.Cloud.Spanner.Data.SpannerException: Insufficient permission to execute the specified operation.
---> Grpc.Core.RpcException: Status(StatusCode="PermissionDenied", Detail="Operation denied by [IAM permission 'spanner.sessions.create' on resource '//spanner.googleapis.com/projects/brighter-464321/instances/brighter-spanner/databases/brightertests'].")
at Google.Api.Gax.Grpc.Gcp.GcpCallInvoker.<>c__DisplayClass24_0`2.<<AsyncUnaryCall>g__PostProcessPropagateResult|3>d.MoveNext()
--- End of stack trace from previous location ---
at Google.Cloud.Spanner.V1.SpannerClientBuilder.RequestIdOnExceptionInterceptor.WrapExceptionAsync[T](Task`1 task, CallOptions options)
at Google.Api.Gax.Grpc.ApiCallRetryExtensions.<>c__DisplayClass0_0`2.<<WithRetry>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at Google.Cloud.Spanner.V1.SessionPool.TargetedSessionPool.CreatePooledSessionsAsync(CancellationToken cancellationToken)
at Google.Cloud.Spanner.V1.SessionPool.TargetedSessionPool.<StartSessionCreationTasksIfNecessary>g__PrepareNewSessionsAsync|39_1()
at Google.Cloud.Spanner.V1.SessionPool.TargetedSessionPool.AcquireSessionImplAsync(TransactionOptions transactionOptions, Boolean singleUseTransaction, Boolean detached, CancellationToken cancellationToken)
at Google.Cloud.Spanner.V1.SessionPool.TargetedSessionPool.AcquireSessionAsync(TransactionOptions transactionOptions, Boolean singleUseTransaction, Boolean detached, CancellationToken cancellationToken)
at Google.Cloud.Spanner.Data.EphemeralTransaction.<>c__DisplayClass9_0.<<Google-Cloud-Spanner-Data-ISpannerTransaction-ExecuteReadOrQueryAsync>g__Impl|0>d.MoveNext()
--- End of stack trace from previous location ---
at Google.Cloud.Spanner.Data.ExecuteHelper.WithErrorTranslationAndProfiling[T](Func`1 t, String name, Logger logger)
at Google.Cloud.Spanner.V1.SessionPool.TargetedSessionPool.AcquireSessionImplAsync(TransactionOptions transactionOptions, Boolean singleUseTransaction, Boolean detached, CancellationToken cancellationToken)
at Google.Cloud.Spanner.V1.SessionPool.TargetedSessionPool.AcquireSessionAsync(TransactionOptions transactionOptions, Boolean singleUseTransaction, Boolean detached, CancellationToken cancellationToken)
at Google.Cloud.Spanner.Data.EphemeralTransaction.<>c__DisplayClass9_0.<<Google-Cloud-Spanner-Data-ISpannerTransaction-ExecuteReadOrQueryAsync>g__Impl|0>d.MoveNext()
--- End of stack trace from previous location ---
at Google.Cloud.Spanner.Data.ExecuteHelper.WithErrorTranslationAndProfiling[T](Func`1 t, String name, Logger logger)
--- End of inner exception stack trace ---
at Google.Cloud.Spanner.Data.ExecuteHelper.WithErrorTranslationAndProfiling[T](Func`1 t, String name, Logger logger)
at Google.Cloud.Spanner.Data.SpannerCommand.ExecutableCommand.ExecuteReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
at Google.Cloud.Spanner.Data.SpannerCommand.ExecutableCommand.ExecuteScalarAsync[T](CancellationToken cancellationToken)
at Paramore.Brighter.BoxProvisioning.Spanner.SpannerBoxDetectionHelper.DoesTableExistAsync(SpannerConnection connection, String tableName, String schemaName, CancellationToken cancellationToken, SpannerTransaction transaction) in /_/src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxDetectionHelper.cs:line 71
at Paramore.Brighter.BoxProvisioning.Spanner.SpannerOutboxProvisioner.DetectTableStateAsync(CancellationToken cancellationToken) in /_/src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerOutboxProvisioner.cs:line 120
at Paramore.Brighter.BoxProvisioning.Spanner.SpannerOutboxProvisioner.ProvisionAsync(CancellationToken cancellationToken) in /_/src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerOutboxProvisioner.cs:line 97
at Paramore.Brighter.Gcp.Tests.Spanner.BoxProvisioning.SpannerConcurrentFreshInstallTests.<>c__DisplayClass4_0.<<Should_not_throw_when_two_concurrent_fresh_installers_race_on_history_insert>b__0>d.MoveNext() in /home/runner/work/Bright
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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'
|
|
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.
|
|
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 boolean conditions. Use Assert.True instead. (https://xunit.net/xunit.analyzers/rules/xUnit2004)
|
|
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
The field 'RmqMessageConsumerConnectionClosedTests._firstException' is 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 variable 'cfe' is declared but never used
|
|
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.
|
|
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.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'
|
|
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.
|
|
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
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.
|
|
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
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:cbbb00015d6357a5f320f7425b9b97fdef3ff6ef6170904a709cebb7b89e7d4e
|
|