chore(deps): bump AWSSDK.SQS from 3.7.400.13 to 3.7.400.20 #5066
Triggered via pull request
September 15, 2024 17:09
Status
Failure
Total duration
4m 25s
Artifacts
–
ci.yml
on: pull_request
build
3m 2s
release
0s
memory
0s
redis-ci
0s
mqtt-ci
0s
rabbitmq-ci
0s
kafka-ci
0s
postgres-ci
0s
sqlserver-ci
0s
mysql-ci
0s
dynamo-ci
0s
aws-ci
0s
sqlite-ci
0s
azure-ci
0s
Annotations
1 error and 10 warnings
build
Process completed with exit code 1.
|
build:
src/Paramore.Brighter/IDistributedLock.cs#L14
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
build:
src/Paramore.Brighter/InMemoryLock.cs#L43
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
build:
src/Paramore.Brighter/InMemoryInbox.cs#L103
Parameter 'TimeProvider timeProvider' is captured into the state of the enclosing type and its value is also passed to the base constructor. The value might be captured by the base class as well.
|
build:
src/Paramore.Brighter/OutboxSweeper.cs#L72
'ApplicationTelemetry' is obsolete: 'Use BrighterTracer instead'
|
build:
src/Paramore.Brighter/OutboxSweeper.cs#L84
'ApplicationTelemetry' is obsolete: 'Use BrighterTracer instead'
|
build:
src/Paramore.Brighter/OutboxArchiver.cs#L64
'ApplicationTelemetry' is obsolete: 'Use BrighterTracer instead'
|
build:
src/Paramore.Brighter/OutboxArchiver.cs#L93
'ApplicationTelemetry' is obsolete: 'Use BrighterTracer instead'
|
build:
src/Paramore.Brighter/IDistributedLock.cs#L14
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
build:
src/Paramore.Brighter/InMemoryLock.cs#L43
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
build:
src/Paramore.Brighter/OutboxSweeper.cs#L72
'ApplicationTelemetry' is obsolete: 'Use BrighterTracer instead'
|