Skip to content
CI

Use isolated dispatch for control message to prevent attaching to outbox's transaction scope if transport supports transaction scopes #1289

Sign in to view logs

Use isolated dispatch for control message to prevent attaching to outbox's transaction scope if transport supports transaction scopes

Use isolated dispatch for control message to prevent attaching to outbox's transaction scope if transport supports transaction scopes #1289

Triggered via pull request January 28, 2025 13:24
@ramonsmitsramonsmits
synchronize #403
use-isolated-dispatch-for-control-message
Status Failure
Total duration 2m 9s
Artifacts –

ci.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

6 errors
Linux: src/NServiceBus.TransactionalSession/OutboxTransactionalSession.cs#L81
'TransportTransaction' does not contain a constructor that takes 1 arguments
Linux: src/NServiceBus.TransactionalSession/OutboxTransactionalSession.cs#L81
'TransportTransaction' does not contain a constructor that takes 1 arguments
Linux
Process completed with exit code 1.
Windows: src/NServiceBus.TransactionalSession/OutboxTransactionalSession.cs#L81
'TransportTransaction' does not contain a constructor that takes 1 arguments
Windows: src/NServiceBus.TransactionalSession/OutboxTransactionalSession.cs#L81
'TransportTransaction' does not contain a constructor that takes 1 arguments
Windows
Process completed with exit code 1.