Skip to content

fix: resolve producer lookup failure when posting Reply messages #7363

fix: resolve producer lookup failure when posting Reply messages

fix: resolve producer lookup failure when posting Reply messages #7363

Triggered via pull request April 25, 2026 19:47
Status Cancelled
Total duration 1h 0m 22s
Artifacts

ci.yml

on: pull_request
release
0s
release
memory
0s
memory
hangfire
0s
hangfire
quartz
0s
quartz
tickerq
0s
tickerq
redis-ci
0s
redis-ci
mqtt-ci
0s
mqtt-ci
rabbitmq-ci
rabbitmq-ci
kafka-ci
kafka-ci
postgres-ci
0s
postgres-ci
sqlserver-ci
sqlserver-ci
mysql-ci
0s
mysql-ci
dynamo-ci
0s
dynamo-ci
localstack-ci
localstack-ci
aws-ci
aws-ci
aws-scheduler-ci
aws-scheduler-ci
sqlite-ci
0s
sqlite-ci
azure-ci
0s
azure-ci
mongodb-ci
mongodb-ci
gcp-ci
gcp-ci
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 10 warnings
build
The job has exceeded the maximum execution time of 1h0m0s
build
The operation was canceled.
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.