[dependabot]

Updated WolverineFx from 6.51.2 to 6.54.0.

Release notes

Sourced from WolverineFx's releases.

6.54.0

Highlights

Dead letter failure groups (#​5209, #​5210). Wolverine now fingerprints every message as it moves to dead letter storage, so dead letters can be managed one failure group at a time:

• The default IDeadLetterFingerprinter hashes the exception type and the first stack frame from application code. Register your own to replace it.
• DeadLetterEnvelopeQuery gains FailureGroup, ExceptionMessageMatch (Exact / Contains), TenantId and Archived.
• A new SummarizeAllAsync overload groups by failure group, message type or endpoint, with first and last failure times.
• ReplayMatchingAsync, DiscardMatchingAsync, ArchiveMatchingAsync and RestoreMatchingAsync report how many dead letters they affected.
• A message that fails again after a replay reports its ReplayCount, LastReplayedAt and FirstFailedAt.
• Archived dead letters drop out of summaries, queries and replays until restored, and can be expired separately with DurabilitySettings.ArchivedDeadLetterRetention.
• IDeadLetters.Capabilities tells you what a store supports.

All changes are additive. The relational stores pick up seven nullable columns on wolverine_dead_letters, an index and a new wolverine_dead_letter_history table through the normal schema migration. See the dead letter storage guide.

Deduplication fixes (#​5205, #​5206, #​5208), and Bobcat 1.0.0-rc.4 dependency pins (#​5211). The WolverineFx.Bobcat* packages remain alpha (6.54.0-alpha.1).

What's Changed

• GH-5205, GH-5206: [DeduplicatedWithResponse] claim-in-transaction gaps ([WriteAggregate] T / [BoundaryModel], and repeats refused over committed work) by @​jeremydmiller in GH-5205, GH-5206: [DeduplicatedWithResponse] claim-in-transaction gaps ([WriteAggregate] T / [BoundaryModel], and repeats refused over committed work) JasperFx/wolverine#5208
• Bobcat 1.0.0-rc.4 by @​jeremydmiller in Bobcat 1.0.0-rc.4 JasperFx/wolverine#5211
• GH-5209 Dead letters: failure fingerprints, operation counts, replay history, archive/restore and tenant scoping by @​jeremydmiller in GH-5209 Dead letters: failure fingerprints, operation counts, replay history, archive/restore and tenant scoping JasperFx/wolverine#5210

Full Changelog: JasperFx/wolverine@V6.53.0...V6.54.0

6.53.0

What's Changed

• GH-5202: keep the ASB response queue identity stable during startup by @​DeandreT in GH-5202: keep the ASB response queue identity stable during startup JasperFx/wolverine#5203

New Contributors

• @​DeandreT made their first contribution in GH-5202: keep the ASB response queue identity stable during startup JasperFx/wolverine#5203

Full Changelog: JasperFx/wolverine@V6.52.0...V6.53.0

6.52.0

Wolverine 6.52.0 is a feature release. The headline items are Aspire-style registration by connection-string name for every transport and every message store, timer agents for short-cadence recurring schedules, and the 6.x groundwork for Wolverine 7.0's one-chain-per-handler model. There are no breaking API changes. Two behavior changes are worth knowing about up front: recurring schedules that fire more often than every 15 minutes now run on a timer agent (opt out per schedule with UseScheduledMessages()), and outgoing envelopes a transport cannot map are dead-lettered instead of being logged and deleted.

Many thanks to everyone who reported issues and sent fixes: @​uniquelau, @​johnkaram02, @​erdtsieck, @​ahmetvayhan and @​pritamrao.

Aspire parity: named connections

• Named-connection overloads for every transport (Aspire parity, GH-5126) by @​jeremydmiller in Named-connection overloads for every transport (Aspire parity, GH-5126) JasperFx/wolverine#5159
• Message storage by connection-string name for every RDBMS provider (PostgreSQL, SQL Server, MySQL, SQLite, Oracle), NpgsqlDataSource / MySqlDataSource from the container, named static tenants, a Named Connection Strings table in describe, and docs that lead with the named form (GH-5127, GH-5156) by @​jeremydmiller in Message storage by connection-string name for every RDBMS provider, plus named-connection docs and describe (GH-5127, GH-5156) JasperFx/wolverine#5174
• Aspire samples moved to Aspire 13.6.3, added to wolverine.slnx, with a ServiceDefaults project for traces, metrics and /health (GH-5124) by @​jeremydmiller in GH-5124 Aspire samples on Aspire 13.6.3 with shared service defaults, in wolverine.slnx JasperFx/wolverine#5182

Messaging and error handling

• Timer agents for short-cadence recurring schedules: one agent per schedule under opts.Schedules.TimerThreshold (15 minutes), same dedup id as the scheduled path, pause and resume through IRecurringScheduleControl (GH-5168) by @​jeremydmiller in GH-5168 Timer-based recurring messages: one agent per short-cadence schedule JasperFx/wolverine#5183
• DoThenRetry(action, maxAttempts) error policy that works both inline and from a queue (GH-5068) by @​jeremydmiller in GH-5068 DoThenRetry() error policy that works inline and from a queue JasperFx/wolverine#5179
• Unmappable outgoing envelopes are dead-lettered on Azure Service Bus, SNS and Kafka instead of being reported as sent (GH-5055) by @​jeremydmiller in GH-5055 Dead letter outgoing envelopes a transport cannot map JasperFx/wolverine#5185
• Durable outbox coalesces stores and deletes per tenant database, so one slow tenant no longer holds back every tenant's sends (GH-5171) by @​jeremydmiller in GH-5171 Coalesce durable outbox/inbox writes per tenant database JasperFx/wolverine#5180
• 6.x prep for HandlerChain 1:1 in 7.0: MultipleHandlerBehavior.ClassicCombineIntoOneLogicalHandler is [Obsolete] (still the default), a startup warning for combined handlers, opt-in AssertNoCombinedHandlers(), fixes for latent Separated bugs, a handler.type OpenTelemetry tag on every chain, and logical deduplication scoped per chain (GH-5133) by @​jeremydmiller in GH-5133 6.x prep for 7.0's one chain per handler type: obsolete ClassicCombine, fix latent Separated bugs, per-handler OTel tag, per-chain dedup scoping JasperFx/wolverine#5184

HTTP

• [DeduplicatedWithResponse] ClaimInTransaction, plus two Marten commit-failure fixes (GH-5160, GH-5165, GH-5166) by @​jeremydmiller with @​uniquelau in GH-5160, GH-5165, GH-5166: [DeduplicatedWithResponse] ClaimInTransaction, plus two Marten commit-failure fixes JasperFx/wolverine#5169
• WolverineHttpOptions.DefaultClaimInTransaction, an application-wide default (GH-5160) by @​jeremydmiller in GH-5160: WolverineHttpOptions.DefaultClaimInTransaction, a global opt-in for [DeduplicatedWithResponse(ClaimInTransaction)] JasperFx/wolverine#5173
• A string response declares its UTF-8 byte count as Content-Length (GH-5187) by @​johnkaram02 in GH-5187: a string response declares its UTF-8 byte count as Content-Length JasperFx/wolverine#5188
• Bind array and list query parameters whose [FromQuery] name is not a C# identifier (GH-5189) by @​johnkaram02 in GH-5189: bind array and list query parameters whose [FromQuery] name is not a C# identifier JasperFx/wolverine#5190

Operability and diagnostics

• ServiceCapabilities reads each store on its own and reports FailedSections, so a failed section is distinguishable from an empty one (GH-5162) by @​jeremydmiller in GH-5162 ServiceCapabilities: isolate each store, record FailedSections JasperFx/wolverine#5175
• AssignmentGrid.Agent.UnplacedReason (AwaitingCapacity, NoCapableNode, Paused, TakeoverHold, Superseded), a capacity log line and an optional NodeAcceptThreshold (GH-5163) by @​jeremydmiller in GH-5163 Unplaced agents carry an UnplacedReason; leader logs agents awaiting capacity JasperFx/wolverine#5176 and GH-5163 follow-up: UnplacedReason names are a stable contract; close the null-reason gaps JasperFx/wolverine#5186
• Header-equality filter on DeadLetterEnvelopeQuery, honored by bulk replay and discard, across every dead letter store (GH-5164) by @​jeremydmiller in GH-5164 DeadLetterEnvelopeQuery header-equality filter JasperFx/wolverine#5181
• db-list / db-dump / db-patch discover the Oracle message store (GH-5172) by @​jeremydmiller in GH-5172 Oracle message store is discoverable by the Weasel db-* commands JasperFx/wolverine#5177

Documentation

• The remaining serverless and Cosmos DB documentation (GH-5054) by @​jeremydmiller in GH-5054 Serverless docs: finish the remaining checklist items JasperFx/wolverine#5178
• Memory sizing for managed event subscription distribution at tenants x projections scale: set MaximumHopperSize to about 2 x BatchSize (GH-5170, follow-up JasperFx/jasperfx#​1076) by @​jeremydmiller in Bump to 6.52.0 JasperFx/wolverine#5199

Full Changelog: JasperFx/wolverine@V6.51.3...V6.52.0

6.51.3

Wolverine 6.51.3 is a durability release. Nearly everything in it came out of a run of reports against the durable inbox and outbox, plus a new durable receiver compliance rig (src/Testing/DurableComplianceRig, Bobcat specs across PostgreSQL, SQL Server, Marten and EF Core over local, database, RabbitMQ and SQS endpoints) that turned up the rest. There are no breaking API changes; the one schema addition (a nullable envelope_id column on the deduplication table) is optional and an unmigrated table keeps working.

Many thanks to everyone who reported these with reproductions: @​billshuck, @​dbelinsky-accureference, @​endava-marinela-marchitan, @​devployment, @​kowalczb, @​Patrick2607 and @​ahmetvayhan.

Durable inbox hardening

• Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split by @​jeremydmiller in Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split JasperFx/wolverine#5129
  • A late DbTransaction dispose in MessageContext.ClearState() could kill another handler's Npgsql transaction
  • Eager idempotency now writes its placeholder inside the handler's transaction (Marten, EF Core, Polecat, Fisher), so a requeued failure is no longer dead lettered as a duplicate of itself
  • EF Core marks the inbox row Handled only after its own commit, and inside the tenant transaction for database-per-tenant
  • A handler that calls ReScheduleAsync and then returns normally keeps its retry
  • A [Deduplicated] claim stranded by a crash can be taken over by the same envelope (new nullable envelope_id column, opt-in IEnvelopeAwareDeduplicationStore)
  • Envelope.DeduplicationId now crosses RabbitMQ, the generic EnvelopeMapper brokers and MQTT
  • Two copies of one envelope in a single batch are reported as DuplicateIncomingEnvelopeException instead of pausing the listener or tripping the tenant write brake (PostgreSQL, SQL Server, MySQL, SQLite, Oracle)
  • RabbitMQ quorum queues: opt-in x-delivery-limit (.DeliveryLimit(n), DeliveryLimitForDurableQuorumQueues(n)), a startup warning, and DeferAsync publishes before it acks. New docs section "Quorum Queues and the Durable Inbox"
• Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues by @​jeremydmiller in Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues JasperFx/wolverine#5157
• Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) by @​jeremydmiller in Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) JasperFx/wolverine#5158

Durable bug fixes

• GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5109
• GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5112
• GH-5107 MySQL queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 MySQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5113
• GH-5107 Oracle queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 Oracle queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5114
• GH-5107 SQLite queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 SQLite queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5115
• GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered by @​jeremydmiller in GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered JasperFx/wolverine#5110
• GH-5108 Logical deduplication claim rides the EF Core transaction by @​jeremydmiller in GH-5108 Logical deduplication claim rides the EF Core transaction JasperFx/wolverine#5111
• GH-5116 A disposed message store refuses a dead letter instead of dropping it by @​jeremydmiller in GH-5116 A disposed message store refuses a dead letter instead of dropping it JasperFx/wolverine#5118
• GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked (durable SQS listeners since 6.40.0) by @​jeremydmiller in GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked JasperFx/wolverine#5121
• GH-5120 A durable batch's scheduled retry is held in memory instead of lost by @​jeremydmiller in GH-5120 A durable batch's scheduled retry is held in memory instead of lost JasperFx/wolverine#5122

Testing

• GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids by @​jeremydmiller in GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids JasperFx/wolverine#5117

Full Changelog: JasperFx/wolverine@V6.51.2...V6.51.3

Commits viewable in compare view.

Updated WolverineFx.AzureServiceBus from 6.51.2 to 6.54.0.

Release notes

Sourced from WolverineFx.AzureServiceBus's releases.

6.54.0

Highlights

Dead letter failure groups (#​5209, #​5210). Wolverine now fingerprints every message as it moves to dead letter storage, so dead letters can be managed one failure group at a time:

• The default IDeadLetterFingerprinter hashes the exception type and the first stack frame from application code. Register your own to replace it.
• DeadLetterEnvelopeQuery gains FailureGroup, ExceptionMessageMatch (Exact / Contains), TenantId and Archived.
• A new SummarizeAllAsync overload groups by failure group, message type or endpoint, with first and last failure times.
• ReplayMatchingAsync, DiscardMatchingAsync, ArchiveMatchingAsync and RestoreMatchingAsync report how many dead letters they affected.
• A message that fails again after a replay reports its ReplayCount, LastReplayedAt and FirstFailedAt.
• Archived dead letters drop out of summaries, queries and replays until restored, and can be expired separately with DurabilitySettings.ArchivedDeadLetterRetention.
• IDeadLetters.Capabilities tells you what a store supports.

All changes are additive. The relational stores pick up seven nullable columns on wolverine_dead_letters, an index and a new wolverine_dead_letter_history table through the normal schema migration. See the dead letter storage guide.

Deduplication fixes (#​5205, #​5206, #​5208), and Bobcat 1.0.0-rc.4 dependency pins (#​5211). The WolverineFx.Bobcat* packages remain alpha (6.54.0-alpha.1).

What's Changed

• GH-5205, GH-5206: [DeduplicatedWithResponse] claim-in-transaction gaps ([WriteAggregate] T / [BoundaryModel], and repeats refused over committed work) by @​jeremydmiller in GH-5205, GH-5206: [DeduplicatedWithResponse] claim-in-transaction gaps ([WriteAggregate] T / [BoundaryModel], and repeats refused over committed work) JasperFx/wolverine#5208
• Bobcat 1.0.0-rc.4 by @​jeremydmiller in Bobcat 1.0.0-rc.4 JasperFx/wolverine#5211
• GH-5209 Dead letters: failure fingerprints, operation counts, replay history, archive/restore and tenant scoping by @​jeremydmiller in GH-5209 Dead letters: failure fingerprints, operation counts, replay history, archive/restore and tenant scoping JasperFx/wolverine#5210

Full Changelog: JasperFx/wolverine@V6.53.0...V6.54.0

6.53.0

What's Changed

• GH-5202: keep the ASB response queue identity stable during startup by @​DeandreT in GH-5202: keep the ASB response queue identity stable during startup JasperFx/wolverine#5203

New Contributors

• @​DeandreT made their first contribution in GH-5202: keep the ASB response queue identity stable during startup JasperFx/wolverine#5203

Full Changelog: JasperFx/wolverine@V6.52.0...V6.53.0

6.52.0

Wolverine 6.52.0 is a feature release. The headline items are Aspire-style registration by connection-string name for every transport and every message store, timer agents for short-cadence recurring schedules, and the 6.x groundwork for Wolverine 7.0's one-chain-per-handler model. There are no breaking API changes. Two behavior changes are worth knowing about up front: recurring schedules that fire more often than every 15 minutes now run on a timer agent (opt out per schedule with UseScheduledMessages()), and outgoing envelopes a transport cannot map are dead-lettered instead of being logged and deleted.

Many thanks to everyone who reported issues and sent fixes: @​uniquelau, @​johnkaram02, @​erdtsieck, @​ahmetvayhan and @​pritamrao.

Aspire parity: named connections

• Named-connection overloads for every transport (Aspire parity, GH-5126) by @​jeremydmiller in Named-connection overloads for every transport (Aspire parity, GH-5126) JasperFx/wolverine#5159
• Message storage by connection-string name for every RDBMS provider (PostgreSQL, SQL Server, MySQL, SQLite, Oracle), NpgsqlDataSource / MySqlDataSource from the container, named static tenants, a Named Connection Strings table in describe, and docs that lead with the named form (GH-5127, GH-5156) by @​jeremydmiller in Message storage by connection-string name for every RDBMS provider, plus named-connection docs and describe (GH-5127, GH-5156) JasperFx/wolverine#5174
• Aspire samples moved to Aspire 13.6.3, added to wolverine.slnx, with a ServiceDefaults project for traces, metrics and /health (GH-5124) by @​jeremydmiller in GH-5124 Aspire samples on Aspire 13.6.3 with shared service defaults, in wolverine.slnx JasperFx/wolverine#5182

Messaging and error handling

• Timer agents for short-cadence recurring schedules: one agent per schedule under opts.Schedules.TimerThreshold (15 minutes), same dedup id as the scheduled path, pause and resume through IRecurringScheduleControl (GH-5168) by @​jeremydmiller in GH-5168 Timer-based recurring messages: one agent per short-cadence schedule JasperFx/wolverine#5183
• DoThenRetry(action, maxAttempts) error policy that works both inline and from a queue (GH-5068) by @​jeremydmiller in GH-5068 DoThenRetry() error policy that works inline and from a queue JasperFx/wolverine#5179
• Unmappable outgoing envelopes are dead-lettered on Azure Service Bus, SNS and Kafka instead of being reported as sent (GH-5055) by @​jeremydmiller in GH-5055 Dead letter outgoing envelopes a transport cannot map JasperFx/wolverine#5185
• Durable outbox coalesces stores and deletes per tenant database, so one slow tenant no longer holds back every tenant's sends (GH-5171) by @​jeremydmiller in GH-5171 Coalesce durable outbox/inbox writes per tenant database JasperFx/wolverine#5180
• 6.x prep for HandlerChain 1:1 in 7.0: MultipleHandlerBehavior.ClassicCombineIntoOneLogicalHandler is [Obsolete] (still the default), a startup warning for combined handlers, opt-in AssertNoCombinedHandlers(), fixes for latent Separated bugs, a handler.type OpenTelemetry tag on every chain, and logical deduplication scoped per chain (GH-5133) by @​jeremydmiller in GH-5133 6.x prep for 7.0's one chain per handler type: obsolete ClassicCombine, fix latent Separated bugs, per-handler OTel tag, per-chain dedup scoping JasperFx/wolverine#5184

HTTP

• [DeduplicatedWithResponse] ClaimInTransaction, plus two Marten commit-failure fixes (GH-5160, GH-5165, GH-5166) by @​jeremydmiller with @​uniquelau in GH-5160, GH-5165, GH-5166: [DeduplicatedWithResponse] ClaimInTransaction, plus two Marten commit-failure fixes JasperFx/wolverine#5169
• WolverineHttpOptions.DefaultClaimInTransaction, an application-wide default (GH-5160) by @​jeremydmiller in GH-5160: WolverineHttpOptions.DefaultClaimInTransaction, a global opt-in for [DeduplicatedWithResponse(ClaimInTransaction)] JasperFx/wolverine#5173
• A string response declares its UTF-8 byte count as Content-Length (GH-5187) by @​johnkaram02 in GH-5187: a string response declares its UTF-8 byte count as Content-Length JasperFx/wolverine#5188
• Bind array and list query parameters whose [FromQuery] name is not a C# identifier (GH-5189) by @​johnkaram02 in GH-5189: bind array and list query parameters whose [FromQuery] name is not a C# identifier JasperFx/wolverine#5190

Operability and diagnostics

• ServiceCapabilities reads each store on its own and reports FailedSections, so a failed section is distinguishable from an empty one (GH-5162) by @​jeremydmiller in GH-5162 ServiceCapabilities: isolate each store, record FailedSections JasperFx/wolverine#5175
• AssignmentGrid.Agent.UnplacedReason (AwaitingCapacity, NoCapableNode, Paused, TakeoverHold, Superseded), a capacity log line and an optional NodeAcceptThreshold (GH-5163) by @​jeremydmiller in GH-5163 Unplaced agents carry an UnplacedReason; leader logs agents awaiting capacity JasperFx/wolverine#5176 and GH-5163 follow-up: UnplacedReason names are a stable contract; close the null-reason gaps JasperFx/wolverine#5186
• Header-equality filter on DeadLetterEnvelopeQuery, honored by bulk replay and discard, across every dead letter store (GH-5164) by @​jeremydmiller in GH-5164 DeadLetterEnvelopeQuery header-equality filter JasperFx/wolverine#5181
• db-list / db-dump / db-patch discover the Oracle message store (GH-5172) by @​jeremydmiller in GH-5172 Oracle message store is discoverable by the Weasel db-* commands JasperFx/wolverine#5177

Documentation

• The remaining serverless and Cosmos DB documentation (GH-5054) by @​jeremydmiller in GH-5054 Serverless docs: finish the remaining checklist items JasperFx/wolverine#5178
• Memory sizing for managed event subscription distribution at tenants x projections scale: set MaximumHopperSize to about 2 x BatchSize (GH-5170, follow-up JasperFx/jasperfx#​1076) by @​jeremydmiller in Bump to 6.52.0 JasperFx/wolverine#5199

Full Changelog: JasperFx/wolverine@V6.51.3...V6.52.0

6.51.3

Wolverine 6.51.3 is a durability release. Nearly everything in it came out of a run of reports against the durable inbox and outbox, plus a new durable receiver compliance rig (src/Testing/DurableComplianceRig, Bobcat specs across PostgreSQL, SQL Server, Marten and EF Core over local, database, RabbitMQ and SQS endpoints) that turned up the rest. There are no breaking API changes; the one schema addition (a nullable envelope_id column on the deduplication table) is optional and an unmigrated table keeps working.

Many thanks to everyone who reported these with reproductions: @​billshuck, @​dbelinsky-accureference, @​endava-marinela-marchitan, @​devployment, @​kowalczb, @​Patrick2607 and @​ahmetvayhan.

Durable inbox hardening

• Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split by @​jeremydmiller in Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split JasperFx/wolverine#5129
  • A late DbTransaction dispose in MessageContext.ClearState() could kill another handler's Npgsql transaction
  • Eager idempotency now writes its placeholder inside the handler's transaction (Marten, EF Core, Polecat, Fisher), so a requeued failure is no longer dead lettered as a duplicate of itself
  • EF Core marks the inbox row Handled only after its own commit, and inside the tenant transaction for database-per-tenant
  • A handler that calls ReScheduleAsync and then returns normally keeps its retry
  • A [Deduplicated] claim stranded by a crash can be taken over by the same envelope (new nullable envelope_id column, opt-in IEnvelopeAwareDeduplicationStore)
  • Envelope.DeduplicationId now crosses RabbitMQ, the generic EnvelopeMapper brokers and MQTT
  • Two copies of one envelope in a single batch are reported as DuplicateIncomingEnvelopeException instead of pausing the listener or tripping the tenant write brake (PostgreSQL, SQL Server, MySQL, SQLite, Oracle)
  • RabbitMQ quorum queues: opt-in x-delivery-limit (.DeliveryLimit(n), DeliveryLimitForDurableQuorumQueues(n)), a startup warning, and DeferAsync publishes before it acks. New docs section "Quorum Queues and the Durable Inbox"
• Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues by @​jeremydmiller in Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues JasperFx/wolverine#5157
• Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) by @​jeremydmiller in Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) JasperFx/wolverine#5158

Durable bug fixes

• GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5109
• GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5112
• GH-5107 MySQL queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 MySQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5113
• GH-5107 Oracle queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 Oracle queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5114
• GH-5107 SQLite queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 SQLite queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5115
• GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered by @​jeremydmiller in GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered JasperFx/wolverine#5110
• GH-5108 Logical deduplication claim rides the EF Core transaction by @​jeremydmiller in GH-5108 Logical deduplication claim rides the EF Core transaction JasperFx/wolverine#5111
• GH-5116 A disposed message store refuses a dead letter instead of dropping it by @​jeremydmiller in GH-5116 A disposed message store refuses a dead letter instead of dropping it JasperFx/wolverine#5118
• GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked (durable SQS listeners since 6.40.0) by @​jeremydmiller in GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked JasperFx/wolverine#5121
• GH-5120 A durable batch's scheduled retry is held in memory instead of lost by @​jeremydmiller in GH-5120 A durable batch's scheduled retry is held in memory instead of lost JasperFx/wolverine#5122

Testing

• GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids by @​jeremydmiller in GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids JasperFx/wolverine#5117

Full Changelog: JasperFx/wolverine@V6.51.2...V6.51.3

Commits viewable in compare view.

Updated WolverineFx.EntityFrameworkCore from 6.51.2 to 6.54.0.

Release notes

Sourced from WolverineFx.EntityFrameworkCore's releases.

6.54.0

Highlights

Dead letter failure groups (#​5209, #​5210). Wolverine now fingerprints every message as it moves to dead letter storage, so dead letters can be managed one failure group at a time:

• The default IDeadLetterFingerprinter hashes the exception type and the first stack frame from application code. Register your own to replace it.
• DeadLetterEnvelopeQuery gains FailureGroup, ExceptionMessageMatch (Exact / Contains), TenantId and Archived.
• A new SummarizeAllAsync overload groups by failure group, message type or endpoint, with first and last failure times.
• ReplayMatchingAsync, DiscardMatchingAsync, ArchiveMatchingAsync and RestoreMatchingAsync report how many dead letters they affected.
• A message that fails again after a replay reports its ReplayCount, LastReplayedAt and FirstFailedAt.
• Archived dead letters drop out of summaries, queries and replays until restored, and can be expired separately with DurabilitySettings.ArchivedDeadLetterRetention.
• IDeadLetters.Capabilities tells you what a store supports.

All changes are additive. The relational stores pick up seven nullable columns on wolverine_dead_letters, an index and a new wolverine_dead_letter_history table through the normal schema migration. See the dead letter storage guide.

Deduplication fixes (#​5205, #​5206, #​5208), and Bobcat 1.0.0-rc.4 dependency pins (#​5211). The WolverineFx.Bobcat* packages remain alpha (6.54.0-alpha.1).

What's Changed

• GH-5205, GH-5206: [DeduplicatedWithResponse] claim-in-transaction gaps ([WriteAggregate] T / [BoundaryModel], and repeats refused over committed work) by @​jeremydmiller in GH-5205, GH-5206: [DeduplicatedWithResponse] claim-in-transaction gaps ([WriteAggregate] T / [BoundaryModel], and repeats refused over committed work) JasperFx/wolverine#5208
• Bobcat 1.0.0-rc.4 by @​jeremydmiller in Bobcat 1.0.0-rc.4 JasperFx/wolverine#5211
• GH-5209 Dead letters: failure fingerprints, operation counts, replay history, archive/restore and tenant scoping by @​jeremydmiller in GH-5209 Dead letters: failure fingerprints, operation counts, replay history, archive/restore and tenant scoping JasperFx/wolverine#5210

Full Changelog: JasperFx/wolverine@V6.53.0...V6.54.0

6.53.0

What's Changed

• GH-5202: keep the ASB response queue identity stable during startup by @​DeandreT in GH-5202: keep the ASB response queue identity stable during startup JasperFx/wolverine#5203

New Contributors

• @​DeandreT made their first contribution in GH-5202: keep the ASB response queue identity stable during startup JasperFx/wolverine#5203

Full Changelog: JasperFx/wolverine@V6.52.0...V6.53.0

6.52.0

Wolverine 6.52.0 is a feature release. The headline items are Aspire-style registration by connection-string name for every transport and every message store, timer agents for short-cadence recurring schedules, and the 6.x groundwork for Wolverine 7.0's one-chain-per-handler model. There are no breaking API changes. Two behavior changes are worth knowing about up front: recurring schedules that fire more often than every 15 minutes now run on a timer agent (opt out per schedule with UseScheduledMessages()), and outgoing envelopes a transport cannot map are dead-lettered instead of being logged and deleted.

Many thanks to everyone who reported issues and sent fixes: @​uniquelau, @​johnkaram02, @​erdtsieck, @​ahmetvayhan and @​pritamrao.

Aspire parity: named connections

• Named-connection overloads for every transport (Aspire parity, GH-5126) by @​jeremydmiller in Named-connection overloads for every transport (Aspire parity, GH-5126) JasperFx/wolverine#5159
• Message storage by connection-string name for every RDBMS provider (PostgreSQL, SQL Server, MySQL, SQLite, Oracle), NpgsqlDataSource / MySqlDataSource from the container, named static tenants, a Named Connection Strings table in describe, and docs that lead with the named form (GH-5127, GH-5156) by @​jeremydmiller in Message storage by connection-string name for every RDBMS provider, plus named-connection docs and describe (GH-5127, GH-5156) JasperFx/wolverine#5174
• Aspire samples moved to Aspire 13.6.3, added to wolverine.slnx, with a ServiceDefaults project for traces, metrics and /health (GH-5124) by @​jeremydmiller in GH-5124 Aspire samples on Aspire 13.6.3 with shared service defaults, in wolverine.slnx JasperFx/wolverine#5182

Messaging and error handling

• Timer agents for short-cadence recurring schedules: one agent per schedule under opts.Schedules.TimerThreshold (15 minutes), same dedup id as the scheduled path, pause and resume through IRecurringScheduleControl (GH-5168) by @​jeremydmiller in GH-5168 Timer-based recurring messages: one agent per short-cadence schedule JasperFx/wolverine#5183
• DoThenRetry(action, maxAttempts) error policy that works both inline and from a queue (GH-5068) by @​jeremydmiller in GH-5068 DoThenRetry() error policy that works inline and from a queue JasperFx/wolverine#5179
• Unmappable outgoing envelopes are dead-lettered on Azure Service Bus, SNS and Kafka instead of being reported as sent (GH-5055) by @​jeremydmiller in GH-5055 Dead letter outgoing envelopes a transport cannot map JasperFx/wolverine#5185
• Durable outbox coalesces stores and deletes per tenant database, so one slow tenant no longer holds back every tenant's sends (GH-5171) by @​jeremydmiller in GH-5171 Coalesce durable outbox/inbox writes per tenant database JasperFx/wolverine#5180
• 6.x prep for HandlerChain 1:1 in 7.0: MultipleHandlerBehavior.ClassicCombineIntoOneLogicalHandler is [Obsolete] (still the default), a startup warning for combined handlers, opt-in AssertNoCombinedHandlers(), fixes for latent Separated bugs, a handler.type OpenTelemetry tag on every chain, and logical deduplication scoped per chain (GH-5133) by @​jeremydmiller in GH-5133 6.x prep for 7.0's one chain per handler type: obsolete ClassicCombine, fix latent Separated bugs, per-handler OTel tag, per-chain dedup scoping JasperFx/wolverine#5184

HTTP

• [DeduplicatedWithResponse] ClaimInTransaction, plus two Marten commit-failure fixes (GH-5160, GH-5165, GH-5166) by @​jeremydmiller with @​uniquelau in GH-5160, GH-5165, GH-5166: [DeduplicatedWithResponse] ClaimInTransaction, plus two Marten commit-failure fixes JasperFx/wolverine#5169
• WolverineHttpOptions.DefaultClaimInTransaction, an application-wide default (GH-5160) by @​jeremydmiller in GH-5160: WolverineHttpOptions.DefaultClaimInTransaction, a global opt-in for [DeduplicatedWithResponse(ClaimInTransaction)] JasperFx/wolverine#5173
• A string response declares its UTF-8 byte count as Content-Length (GH-5187) by @​johnkaram02 in GH-5187: a string response declares its UTF-8 byte count as Content-Length JasperFx/wolverine#5188
• Bind array and list query parameters whose [FromQuery] name is not a C# identifier (GH-5189) by @​johnkaram02 in GH-5189: bind array and list query parameters whose [FromQuery] name is not a C# identifier JasperFx/wolverine#5190

Operability and diagnostics

• ServiceCapabilities reads each store on its own and reports FailedSections, so a failed section is distinguishable from an empty one (GH-5162) by @​jeremydmiller in GH-5162 ServiceCapabilities: isolate each store, record FailedSections JasperFx/wolverine#5175
• AssignmentGrid.Agent.UnplacedReason (AwaitingCapacity, NoCapableNode, Paused, TakeoverHold, Superseded), a capacity log line and an optional NodeAcceptThreshold (GH-5163) by @​jeremydmiller in GH-5163 Unplaced agents carry an UnplacedReason; leader logs agents awaiting capacity JasperFx/wolverine#5176 and GH-5163 follow-up: UnplacedReason names are a stable contract; close the null-reason gaps JasperFx/wolverine#5186
• Header-equality filter on DeadLetterEnvelopeQuery, honored by bulk replay and discard, across every dead letter store (GH-5164) by @​jeremydmiller in GH-5164 DeadLetterEnvelopeQuery header-equality filter JasperFx/wolverine#5181
• db-list / db-dump / db-patch discover the Oracle message store (GH-5172) by @​jeremydmiller in GH-5172 Oracle message store is discoverable by the Weasel db-* commands JasperFx/wolverine#5177

Documentation

• The remaining serverless and Cosmos DB documentation (GH-5054) by @​jeremydmiller in GH-5054 Serverless docs: finish the remaining checklist items JasperFx/wolverine#5178
• Memory sizing for managed event subscription distribution at tenants x projections scale: set MaximumHopperSize to about 2 x BatchSize (GH-5170, follow-up JasperFx/jasperfx#​1076) by @​jeremydmiller in Bump to 6.52.0 JasperFx/wolverine#5199

Full Changelog: JasperFx/wolverine@V6.51.3...V6.52.0

6.51.3

Wolverine 6.51.3 is a durability release. Nearly everything in it came out of a run of reports against the durable inbox and outbox, plus a new durable receiver compliance rig (src/Testing/DurableComplianceRig, Bobcat specs across PostgreSQL, SQL Server, Marten and EF Core over local, database, RabbitMQ and SQS endpoints) that turned up the rest. There are no breaking API changes; the one schema addition (a nullable envelope_id column on the deduplication table) is optional and an unmigrated table keeps working.

Many thanks to everyone who reported these with reproductions: @​billshuck, @​dbelinsky-accureference, @​endava-marinela-marchitan, @​devployment, @​kowalczb, @​Patrick2607 and @​ahmetvayhan.

Durable inbox hardening

• Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split by @​jeremydmiller in Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split JasperFx/wolverine#5129
  • A late DbTransaction dispose in MessageContext.ClearState() could kill another handler's Npgsql transaction
  • Eager idempotency now writes its placeholder inside the handler's transaction (Marten, EF Core, Polecat, Fisher), so a requeued failure is no longer dead lettered as a duplicate of itself
  • EF Core marks the inbox row Handled only after its own commit, and inside the tenant transaction for database-per-tenant
  • A handler that calls ReScheduleAsync and then returns normally keeps its retry
  • A [Deduplicated] claim stranded by a crash can be taken over by the same envelope (new nullable envelope_id column, opt-in IEnvelopeAwareDeduplicationStore)
  • Envelope.DeduplicationId now crosses RabbitMQ, the generic EnvelopeMapper brokers and MQTT
  • Two copies of one envelope in a single batch are reported as DuplicateIncomingEnvelopeException instead of pausing the listener or tripping the tenant write brake (PostgreSQL, SQL Server, MySQL, SQLite, Oracle)
  • RabbitMQ quorum queues: opt-in x-delivery-limit (.DeliveryLimit(n), DeliveryLimitForDurableQuorumQueues(n)), a startup warning, and DeferAsync publishes before it acks. New docs section "Quorum Queues and the Durable Inbox"
• Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues by @​jeremydmiller in Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues JasperFx/wolverine#5157
• Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) by @​jeremydmiller in Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) JasperFx/wolverine#5158

Durable bug fixes

• GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5109
• GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5112
• GH-5107 MySQL queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 MySQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5113
• GH-5107 Oracle queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 Oracle queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5114
• GH-5107 SQLite queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 SQLite queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5115
• GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered by @​jeremydmiller in GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered JasperFx/wolverine#5110
• GH-5108 Logical deduplication claim rides the EF Core transaction by @​jeremydmiller in GH-5108 Logical deduplication claim rides the EF Core transaction JasperFx/wolverine#5111
• GH-5116 A disposed message store refuses a dead letter instead of dropping it by @​jeremydmiller in GH-5116 A disposed message store refuses a dead letter instead of dropping it JasperFx/wolverine#5118
• GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked (durable SQS listeners since 6.40.0) by @​jeremydmiller in GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked JasperFx/wolverine#5121
• GH-5120 A durable batch's scheduled retry is held in memory instead of lost by @​jeremydmiller in GH-5120 A durable batch's scheduled retry is held in memory instead of lost JasperFx/wolverine#5122

Testing

• GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids by @​jeremydmiller in GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids JasperFx/wolverine#5117

Full Changelog: JasperFx/wolverine@V6.51.2...V6.51.3

Commits viewable in compare view.

Updated WolverineFx.RuntimeCompilation from 6.51.2 to 6.54.0.

Release notes

Sourced from WolverineFx.RuntimeCompilation's releases.

6.54.0

Highlights

Dead letter failure groups (#​5209, #​5210). Wolverine now fingerprints every message as it moves to dead letter storage, so dead letters can be managed one failure group at a time:

• The default IDeadLetterFingerprinter hashes the exception type and the first stack frame from application code. Register your own to replace it.
• DeadLetterEnvelopeQuery gains FailureGroup, ExceptionMessageMatch (Exact / Contains), TenantId and Archived.
• A new SummarizeAllAsync overload groups by failure group, message type or endpoint, with first and last failure times.
• ReplayMatchingAsync, DiscardMatchingAsync, ArchiveMatchingAsync and RestoreMatchingAsync report how many dead letters they affected.
• A message that fails again after a replay reports its ReplayCount, LastReplayedAt and FirstFailedAt.
• Archived dead letters drop out of summaries, queries and replays until restored, and can be expired separately with DurabilitySettings.ArchivedDeadLetterRetention.
• IDeadLetters.Capabilities tells you what a store supports.

All changes are additive. The relational stores pick up seven nullable columns on wolverine_dead_letters, an index and a new wolverine_dead_letter_history table through the normal schema migration. See the dead letter storage guide.

Deduplication fixes (#​5205, #​5206, #​5208), and Bobcat 1.0.0-rc.4 dependency pins (#​5211). The WolverineFx.Bobcat* packages remain alpha (6.54.0-alpha.1).

What's Changed

• GH-5205, GH-5206: [DeduplicatedWithResponse] claim-in-transaction gaps ([WriteAggregate] T / [BoundaryModel], and repeats refused over committed work) by @​jeremydmiller in GH-5205, GH-5206: [DeduplicatedWithResponse] claim-in-transaction gaps ([WriteAggregate] T / [BoundaryModel], and repeats refused over committed work) JasperFx/wolverine#5208
• Bobcat 1.0.0-rc.4 by @​jeremydmiller in Bobcat 1.0.0-rc.4 JasperFx/wolverine#5211
• GH-5209 Dead letters: failure fingerprints, operation counts, replay history, archive/restore and tenant scoping by @​jeremydmiller in GH-5209 Dead letters: failure fingerprints, operation counts, replay history, archive/restore and tenant scoping JasperFx/wolverine#5210

Full Changelog: JasperFx/wolverine@V6.53.0...V6.54.0

6.53.0

What's Changed

• GH-5202: keep the ASB response queue identity stable during startup by @​DeandreT in GH-5202: keep the ASB response queue identity stable during startup JasperFx/wolverine#5203

New Contributors

• @​DeandreT made their first contribution in GH-5202: keep the ASB response queue identity stable during startup JasperFx/wolverine#5203

Full Changelog: JasperFx/wolverine@V6.52.0...V6.53.0

6.52.0

Wolverine 6.52.0 is a feature release. The headline items are Aspire-style registration by connection-string name for every transport and every message store, timer agents for short-cadence recurring schedules, and the 6.x groundwork for Wolverine 7.0's one-chain-per-handler model. There are no breaking API changes. Two behavior changes are worth knowing about up front: recurring schedules that fire more often than every 15 minutes now run on a timer agent (opt out per schedule with UseScheduledMessages()), and outgoing envelopes a transport cannot map are dead-lettered instead of being logged and deleted.

Many thanks to everyone who reported issues and sent fixes: @​uniquelau, @​johnkaram02, @​erdtsieck, @​ahmetvayhan and @​pritamrao.

Aspire parity: named connections

• Named-connection overloads for every transport (Aspire parity, GH-5126) by @​jeremydmiller in Named-connection overloads for every transport (Aspire parity, GH-5126) JasperFx/wolverine#5159
• Message storage by connection-string name for every RDBMS provider (PostgreSQL, SQL Server, MySQL, SQLite, Oracle), NpgsqlDataSource / MySqlDataSource from the container, named static tenants, a Named Connection Strings table in describe, and docs that lead with the named form (GH-5127, GH-5156) by @​jeremydmiller in Message storage by connection-string name for every RDBMS provider, plus named-connection docs and describe (GH-5127, GH-5156) JasperFx/wolverine#5174
• Aspire samples moved to Aspire 13.6.3, added to wolverine.slnx, with a ServiceDefaults project for traces, metrics and /health (GH-5124) by @​jeremydmiller in GH-5124 Aspire samples on Aspire 13.6.3 with shared service defaults, in wolverine.slnx JasperFx/wolverine#5182

Messaging and error handling

• Timer agents for short-cadence recurring schedules: one agent per schedule under opts.Schedules.TimerThreshold (15 minutes), same dedup id as the scheduled path, pause and resume through IRecurringScheduleControl (GH-5168) by @​jeremydmiller in GH-5168 Timer-based recurring messages: one agent per short-cadence schedule JasperFx/wolverine#5183
• DoThenRetry(action, maxAttempts) error policy that works both inline and from a queue (GH-5068) by @​jeremydmiller in GH-5068 DoThenRetry() error policy that works inline and from a queue JasperFx/wolverine#5179
• Unmappable outgoing envelopes are dead-lettered on Azure Service Bus, SNS and Kafka instead of being reported as sent (GH-5055) by @​jeremydmiller in GH-5055 Dead letter outgoing envelopes a transport cannot map JasperFx/wolverine#5185
• Durable outbox coalesces stores and deletes per tenant database, so one slow tenant no longer holds back every tenant's sends (GH-5171) by @​jeremydmiller in GH-5171 Coalesce durable outbox/inbox writes per tenant database JasperFx/wolverine#5180
• 6.x prep for HandlerChain 1:1 in 7.0: MultipleHandlerBehavior.ClassicCombineIntoOneLogicalHandler is [Obsolete] (still the default), a startup warning for combined handlers, opt-in AssertNoCombinedHandlers(), fixes for latent Separated bugs, a handler.type OpenTelemetry tag on every chain, and logical deduplication scoped per chain (GH-5133) by @​jeremydmiller in GH-5133 6.x prep for 7.0's one chain per handler type: obsolete ClassicCombine, fix latent Separated bugs, per-handler OTel tag, per-chain dedup scoping JasperFx/wolverine#5184

HTTP

• [DeduplicatedWithResponse] ClaimInTransaction, plus two Marten commit-failure fixes (GH-5160, GH-5165, GH-5166) by @​jeremydmiller with @​uniquelau in GH-5160, GH-5165, GH-5166: [DeduplicatedWithResponse] ClaimInTransaction, plus two Marten commit-failure fixes JasperFx/wolverine#5169
• WolverineHttpOptions.DefaultClaimInTransaction, an application-wide default (GH-5160) by @​jeremydmiller in GH-5160: WolverineHttpOptions.DefaultClaimInTransaction, a global opt-in for [DeduplicatedWithResponse(ClaimInTransaction)] JasperFx/wolverine#5173
• A string response declares its UTF-8 byte count as Content-Length (GH-5187) by @​johnkaram02 in GH-5187: a string response declares its UTF-8 byte count as Content-Length JasperFx/wolverine#5188
• Bind array and list query parameters whose [FromQuery] name is not a C# identifier (GH-5189) by @​johnkaram02 in GH-5189: bind array and list query parameters whose [FromQuery] name is not a C# identifier JasperFx/wolverine#5190

Operability and diagnostics

• ServiceCapabilities reads each store on its own and reports FailedSections, so a failed section is distinguishable from an empty one (GH-5162) by @​jeremydmiller in GH-5162 ServiceCapabilities: isolate each store, record FailedSections JasperFx/wolverine#5175
• AssignmentGrid.Agent.UnplacedReason (AwaitingCapacity, NoCapableNode, Paused, TakeoverHold, Superseded), a capacity log line and an optional NodeAcceptThreshold (GH-5163) by @​jeremydmiller in GH-5163 Unplaced agents carry an UnplacedReason; leader logs agents awaiting capacity JasperFx/wolverine#5176 and GH-5163 follow-up: UnplacedReason names are a stable contract; close the null-reason gaps JasperFx/wolverine#5186
• Header-equality filter on DeadLetterEnvelopeQuery, honored by bulk replay and discard, across every dead letter store (GH-5164) by @​jeremydmiller in GH-5164 DeadLetterEnvelopeQuery header-equality filter JasperFx/wolverine#5181
• db-list / db-dump / db-patch discover the Oracle message store (GH-5172) by @​jeremydmiller in GH-5172 Oracle message store is discoverable by the Weasel db-* commands JasperFx/wolverine#5177

Documentation

• The remaining serverless and Cosmos DB documentation (GH-5054) by @​jeremydmiller in GH-5054 Serverless docs: finish the remaining checklist items JasperFx/wolverine#5178
• Memory sizing for managed event subscription distribution at tenants x projections scale: set MaximumHopperSize to about 2 x BatchSize (GH-5170, follow-up JasperFx/jasperfx#​1076) by @​jeremydmiller in Bump to 6.52.0 JasperFx/wolverine#5199

Full Changelog: JasperFx/wolverine@V6.51.3...V6.52.0

6.51.3

Wolverine 6.51.3 is a durability release. Nearly everything in it came out of a run of reports against the durable inbox and outbox, plus a new durable receiver compliance rig (src/Testing/DurableComplianceRig, Bobcat specs across PostgreSQL, SQL Server, Marten and EF Core over local, database, RabbitMQ and SQS endpoints) that turned up the rest. There are no breaking API changes; the one schema addition (a nullable envelope_id column on the deduplication table) is optional and an unmigrated table keeps working.

Many thanks to everyone who reported these with reproductions: @​billshuck, @​dbelinsky-accureference, @​endava-marinela-marchitan, @​devployment, @​kowalczb, @​Patrick2607 and @​ahmetvayhan.

Durable inbox hardening

• Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split by @​jeremydmiller in Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split JasperFx/wolverine#5129
  • A late DbTransaction dispose in MessageContext.ClearState() could kill another handler's Npgsql transaction
  • Eager idempotency now writes its placeholder inside the handler's transaction (Marten, EF Core, Polecat, Fisher), so a requeued failure is no longer dead lettered as a duplicate of itself
  • EF Core marks the inbox row Handled only after its own commit, and inside the tenant transaction for database-per-tenant
  • A handler that calls ReScheduleAsync and then returns normally keeps its retry
  • A [Deduplicated] claim stranded by a crash can be taken over by the same envelope (new nullable envelope_id column, opt-in IEnvelopeAwareDeduplicationStore)
  • Envelope.DeduplicationId now crosses RabbitMQ, the generic EnvelopeMapper brokers and MQTT
  • Two copies of one envelope in a single batch are reported as DuplicateIncomingEnvelopeException instead of pausing the listener or tripping the tenant write brake (PostgreSQL, SQL Server, MySQL, SQLite, Oracle)
  • RabbitMQ quorum queues: opt-in x-delivery-limit (.DeliveryLimit(n), DeliveryLimitForDurableQuorumQueues(n)), a startup warning, and DeferAsync publishes before it acks. New docs section "Quorum Queues and the Durable Inbox"
• Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues by @​jeremydmiller in Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues JasperFx/wolverine#5157
• Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) by @​jeremydmiller in Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) JasperFx/wolverine#5158

Durable bug fixes

• GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5109
• GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5112
• GH-5107 MySQL queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 MySQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5113
• GH-5107 Oracle queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 Oracle queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5114
• GH-5107 SQLite queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 SQLite queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5115
• GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered by @​jeremydmiller in GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered JasperFx/wolverine#5110
• GH-5108 Logical deduplication claim rides the EF Core transaction by @​jeremydmiller in GH-5108 Logical deduplication claim rides the EF Core transaction JasperFx/wolverine#5111
• GH-5116 A disposed message store refuses a dead letter instead of dropping it by @​jeremydmiller in GH-5116 A disposed message store refuses a dead letter instead of dropping it JasperFx/wolverine#5118
• GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked (durable SQS listeners since 6.40.0) by @​jeremydmiller in GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked JasperFx/wolverine#5121
• GH-5120 A durable batch's scheduled retry is held in memory instead of lost by @​jeremydmiller in GH-5120 A durable batch's scheduled retry is held in memory instead of lost JasperFx/wolverine#5122

Testing

• GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids by @​jeremydmiller in GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids JasperFx/wolverine#5117

Full Changelog: JasperFx/wolverine@V6.51.2...V6.51.3

Commits viewable in compare view.

Updated WolverineFx.SqlServer from 6.51.2 to 6.54.0.

Release notes

Sourced from WolverineFx.SqlServer's releases.

6.54.0

Highlights

Dead letter failure groups (#​5209, #​5210). Wolverine now fingerprints every message as it moves to dead letter storage, so dead letters can be managed one failure group at a time:

• The default IDeadLetterFingerprinter hashes the exception type and the first stack frame from application code. Register your own to replace it.
• DeadLetterEnvelopeQuery gains FailureGroup, ExceptionMessageMatch (Exact / Contains), TenantId and Archived.
• A new SummarizeAllAsync overload groups by failure group, message type or endpoint, with first and last failure times.
• ReplayMatchingAsync, DiscardMatchingAsync, ArchiveMatchingAsync and RestoreMatchingAsync report how many dead letters they affected.
• A message that fails again after a replay reports its ReplayCount, LastReplayedAt and FirstFailedAt.
• Archived dead letters drop out of summaries, queries and replays until restored, and can be expired separately with DurabilitySettings.ArchivedDeadLetterRetention.
• IDeadLetters.Capabilities tells you what a store supports.

All changes are additive. The relational stores pick up seven nullable columns on wolverine_dead_letters, an index and a new wolverine_dead_letter_history table through the normal schema migration. See the dead letter storage guide.

Deduplication fixes (#​5205, #​5206, #​5208), and Bobcat 1.0.0-rc.4 dependency pins (#​5211). The WolverineFx.Bobcat* packages remain alpha (6.54.0-alpha.1).

What's Changed

• GH-5205, GH-5206: [DeduplicatedWithResponse] claim-in-transaction gaps ([WriteAggregate] T / [BoundaryModel], and repeats refused over committed work) by @​jeremydmiller in GH-5205, GH-5206: [DeduplicatedWithResponse] claim-in-transaction gaps ([WriteAggregate] T / [BoundaryModel], and repeats refused over committed work) JasperFx/wolverine#5208
• Bobcat 1.0.0-rc.4 by @​jeremydmiller in Bobcat 1.0.0-rc.4 JasperFx/wolverine#5211
• GH-5209 Dead letters: failure fingerprints, operation counts, replay history, archive/restore and tenant scoping by @​jeremydmiller in GH-5209 Dead letters: failure fingerprints, operation counts, replay history, archive/restore and tenant scoping JasperFx/wolverine#5210

Full Changelog: JasperFx/wolverine@V6.53.0...V6.54.0

6.53.0

What's Changed

• GH-5202: keep the ASB response queue identity stable during startup by @​DeandreT in GH-5202: keep the ASB response queue identity stable during startup JasperFx/wolverine#5203

New Contributors

• @​DeandreT made their first contribution in GH-5202: keep the ASB response queue identity stable during startup JasperFx/wolverine#5203

Full Changelog: JasperFx/wolverine@V6.52.0...V6.53.0

6.52.0

Wolverine 6.52.0 is a feature release. The headline items are Aspire-style registration by connection-string name for every transport and every message store, timer agents for short-cadence recurring schedules, and the 6.x groundwork for Wolverine 7.0's one-chain-per-handler model. There are no breaking API changes. Two behavior changes are worth knowing about up front: recurring schedules that fire more often than every 15 minutes now run on a timer agent (opt out per schedule with UseScheduledMessages()), and outgoing envelopes a transport cannot map are dead-lettered instead of being logged and deleted.

Many thanks to everyone who reported issues and sent fixes: @​uniquelau, @​johnkaram02, @​erdtsieck, @​ahmetvayhan and @​pritamrao.

Aspire parity: named connections

• Named-connection overloads for every transport (Aspire parity, GH-5126) by @​jeremydmiller in Named-connection overloads for every transport (Aspire parity, GH-5126) JasperFx/wolverine#5159
• Message storage by connection-string name for every RDBMS provider (PostgreSQL, SQL Server, MySQL, SQLite, Oracle), NpgsqlDataSource / MySqlDataSource from the container, named static tenants, a Named Connection Strings table in describe, and docs that lead with the named form (GH-5127, GH-5156) by @​jeremydmiller in Message storage by connection-string name for every RDBMS provider, plus named-connection docs and describe (GH-5127, GH-5156) JasperFx/wolverine#5174
• Aspire samples moved to Aspire 13.6.3, added to wolverine.slnx, with a ServiceDefaults project for traces, metrics and /health (GH-5124) by @​jeremydmiller in GH-5124 Aspire samples on Aspire 13.6.3 with shared service defaults, in wolverine.slnx JasperFx/wolverine#5182

Messaging and error handling

• Timer agents for short-cadence recurring schedules: one agent per schedule under opts.Schedules.TimerThreshold (15 minutes), same dedup id as the scheduled path, pause and resume through IRecurringScheduleControl (GH-5168) by @​jeremydmiller in GH-5168 Timer-based recurring messages: one agent per short-cadence schedule JasperFx/wolverine#5183
• DoThenRetry(action, maxAttempts) error policy that works both inline and from a queue (GH-5068) by @​jeremydmiller in GH-5068 DoThenRetry() error policy that works inline and from a queue JasperFx/wolverine#5179
• Unmappable outgoing envelopes are dead-lettered on Azure Service Bus, SNS and Kafka instead of being reported as sent (GH-5055) by @​jeremydmiller in GH-5055 Dead letter outgoing envelopes a transport cannot map JasperFx/wolverine#5185
• Durable outbox coalesces stores and deletes per tenant database, so one slow tenant no longer holds back every tenant's sends (GH-5171) by @​jeremydmiller in GH-5171 Coalesce durable outbox/inbox writes per tenant database JasperFx/wolverine#5180
• 6.x prep for HandlerChain 1:1 in 7.0: MultipleHandlerBehavior.ClassicCombineIntoOneLogicalHandler is [Obsolete] (still the default), a startup warning for combined handlers, opt-in AssertNoCombinedHandlers(), fixes for latent Separated bugs, a handler.type OpenTelemetry tag on every chain, and logical deduplication scoped per chain (GH-5133) by @​jeremydmiller in GH-5133 6.x prep for 7.0's one chain per handler type: obsolete ClassicCombine, fix latent Separated bugs, per-handler OTel tag, per-chain dedup scoping JasperFx/wolverine#5184

HTTP

• [DeduplicatedWithResponse] ClaimInTransaction, plus two Marten commit-failure fixes (GH-5160, GH-5165, GH-5166) by @​jeremydmiller with @​uniquelau in GH-5160, GH-5165, GH-5166: [DeduplicatedWithResponse] ClaimInTransaction, plus two Marten commit-failure fixes JasperFx/wolverine#5169
• WolverineHttpOptions.DefaultClaimInTransaction, an application-wide default (GH-5160) by @​jeremydmiller in GH-5160: WolverineHttpOptions.DefaultClaimInTransaction, a global opt-in for [DeduplicatedWithResponse(ClaimInTransaction)] JasperFx/wolverine#5173
• A string response declares its UTF-8 byte count as Content-Length (GH-5187) by @​johnkaram02 in GH-5187: a string response declares its UTF-8 byte count as Content-Length JasperFx/wolverine#5188
• Bind array and list query parameters whose [FromQuery] name is not a C# identifier (GH-5189) by @​johnkaram02 in GH-5189: bind array and list query parameters whose [FromQuery] name is not a C# identifier JasperFx/wolverine#5190

Operability and diagnostics

• ServiceCapabilities reads each store on its own and reports FailedSections, so a failed section is distinguishable from an empty one (GH-5162) by @​jeremydmiller in GH-5162 ServiceCapabilities: isolate each store, record FailedSections JasperFx/wolverine#5175
• AssignmentGrid.Agent.UnplacedReason (AwaitingCapacity, NoCapableNode, Paused, TakeoverHold, Superseded), a capacity log line and an optional NodeAcceptThreshold (GH-5163) by @​jeremydmiller in GH-5163 Unplaced agents carry an UnplacedReason; leader logs agents awaiting capacity JasperFx/wolverine#5176 and GH-5163 follow-up: UnplacedReason names are a stable contract; close the null-reason gaps JasperFx/wolverine#5186
• Header-equality filter on DeadLetterEnvelopeQuery, honored by bulk replay and discard, across every dead letter store (GH-5164) by @​jeremydmiller in GH-5164 DeadLetterEnvelopeQuery header-equality filter JasperFx/wolverine#5181
• db-list / db-dump / db-patch discover the Oracle message store (GH-5172) by @​jeremydmiller in GH-5172 Oracle message store is discoverable by the Weasel db-* commands JasperFx/wolverine#5177

Documentation

• The remaining serverless and Cosmos DB documentation (GH-5054) by @​jeremydmiller in GH-5054 Serverless docs: finish the remaining checklist items JasperFx/wolverine#5178
• Memory sizing for managed event subscription distribution at tenants x projections scale: set MaximumHopperSize to about 2 x BatchSize (GH-5170, follow-up JasperFx/jasperfx#​1076) by @​jeremydmiller in Bump to 6.52.0 JasperFx/wolverine#5199

Full Changelog: JasperFx/wolverine@V6.51.3...V6.52.0

6.51.3

Wolverine 6.51.3 is a durability release. Nearly everything in it came out of a run of reports against the durable inbox and outbox, plus a new durable receiver compliance rig (src/Testing/DurableComplianceRig, Bobcat specs across PostgreSQL, SQL Server, Marten and EF Core over local, database, RabbitMQ and SQS endpoints) that turned up the rest. There are no breaking API changes; the one schema addition (a nullable envelope_id column on the deduplication table) is optional and an unmigrated table keeps working.

Many thanks to everyone who reported these with reproductions: @​billshuck, @​dbelinsky-accureference, @​endava-marinela-marchitan, @​devployment, @​kowalczb, @​Patrick2607 and @​ahmetvayhan.

Durable inbox hardening

• Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split by @​jeremydmiller in Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split JasperFx/wolverine#5129
  • A late DbTransaction dispose in MessageContext.ClearState() could kill another handler's Npgsql transaction
  • Eager idempotency now writes its placeholder inside the handler's transaction (Marten, EF Core, Polecat, Fisher), so a requeued failure is no longer dead lettered as a duplicate of itself
  • EF Core marks the inbox row Handled only after its own commit, and inside the tenant transaction for database-per-tenant
  • A handler that calls ReScheduleAsync and then returns normally keeps its retry
  • A [Deduplicated] claim stranded by a crash can be taken over by the same envelope (new nullable envelope_id column, opt-in IEnvelopeAwareDeduplicationStore)
  • Envelope.DeduplicationId now crosses RabbitMQ, the generic EnvelopeMapper brokers and MQTT
  • Two copies of one envelope in a single batch are reported as DuplicateIncomingEnvelopeException instead of pausing the listener or tripping the tenant write brake (PostgreSQL, SQL Server, MySQL, SQLite, Oracle)
  • RabbitMQ quorum queues: opt-in x-delivery-limit (.DeliveryLimit(n), DeliveryLimitForDurableQuorumQueues(n)), a startup warning, and DeferAsync publishes before it acks. New docs section "Quorum Queues and the Durable Inbox"
• Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues by @​jeremydmiller in Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues JasperFx/wolverine#5157
• Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) by @​jeremydmiller in Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) JasperFx/wolverine#5158

Durable bug fixes

• GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5109
• GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5112
• GH-5107 MySQL queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 MySQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5113
• GH-5107 Oracle queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 Oracle queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5114
• GH-5107 SQLite queue sender moves the outbox row atomically for every durable send by @​jeremydmiller in GH-5107 SQLite queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5115
• GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered by @​jeremydmiller in GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered JasperFx/wolverine#5110
• GH-5108 Logical deduplication claim rides the EF Core transaction by @​jeremydmiller in GH-5108 Logical deduplication claim rides the EF Core transaction JasperFx/wolverine#5111
• GH-5116 A disposed message store refuses a dead letter instead of dropping it by @​jeremydmiller in GH-5116 A disposed message store refuses a dead letter instead of dropping it JasperFx/wolverine#5118
• GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked (durable SQS listeners since 6.40.0) by @​jeremydmiller in GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked JasperFx/wolverine#5121
• GH-5120 A durable batch's scheduled retry is held in memory instead of lost by @​jeremydmiller in GH-5120 A durable batch's scheduled retry is held in memory instead of lost JasperFx/wolverine#5122

Testing

• GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids by @​jeremydmiller in GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids JasperFx/wolverine#5117

Full Changelog: JasperFx/wolverine@V6.51.2...V6.51.3

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions