Bump WolverineFx from 6.24.4 to 6.24.6

[dependabot]

Updated WolverineFx from 6.24.4 to 6.24.6.

Release notes

Sourced from WolverineFx's releases.

6.24.6

A bug-fix release. The headline is a message ordering regression affecting every transport built on BatchedSender — if you rely on FIFO ordering anywhere, this release matters to you.

Highlights

Message ordering restored in BatchedSender (#​3825). BatchedSender ran its serializing stage at Environment.ProcessorCount, so envelopes reached the batching block in serialization-completion order rather than enqueue order.

This was a silent regression from the switch off TPL Dataflow. ActionBlock defaults MaxDegreeOfParallelism to 1 — ordered by default — and the Channels rewrite raised it without the ordering guarantee being restated anywhere. The block was ordered for years, then quietly wasn't. The practical effect: FIFO ordering was not honored under Azure Service Bus sessions, SQS FIFO message groups, or global partitioning, on every transport that uses BatchedSender. Nothing was lost; messages arrived out of order. Fixed by returning the stage to a degree of parallelism of 1 — everything downstream was already serial.

A second, independent defect fell out of the same investigation: TrackedSession.AllRecordsInOrder() sorted by SessionTime, which is ElapsedMilliseconds — whole milliseconds. An entire receive batch ties, and the stable sort then fell back to enumerating a Guid-keyed cache with no relation to real order. Every ordering assertion in the test suite was at the mercy of this. Records now carry a monotonic sequence number.

Back-pressure now works on the right number, and says what it is (#​3831, jasperfx#​632). A latched listener logged exactly one too busy line and then nothing — forever. An operator watching a queue grow for 40 minutes could not distinguish "still draining" from "wedged". Underneath that, the count a PartitionProcessingByGroupId endpoint latched and resumed against was wrong: the downstream block holding the backlog was invisible to it, so Count reported zero for work that was really there.

• BackPressureAgent logs a periodic warning while a listener stays latched, carrying the queue count and the restart threshold the resume decision is made from.
• The timer-driven check is exception-safe. A throw during an attempted resume was an unobserved ValueTask fault, and the listener silently never resumed.
• BufferedReceiver/DurableReceiver wire the receiving block's OnError to ILogger. A terminally-faulted block freezes the queue count and permanently latches the listener; that now logs at Critical instead of vanishing to stderr.

A tenanted Azure Service Bus endpoint could not send at all (#​3826) — tenanted or untenanted. TenantedSender deliberately does not implement ISenderRequiresCallback, but callback registration did not recurse, so a BatchedSender underneath it kept a null callback and threw InvalidOperationException: This sender has not been registered. on every batch. The tenanted path now uses inline senders, matching how Redis, MQTT, and Pub/Sub already worked around this.

Oracle queue identity round-trip (#​3820). System.Uri lowercases the authority component while Oracle uppercases its queue identifiers, so ToOracleQueue() resolved a second endpoint over the same physical tables. Also fixes a dead final-attempt error handler: a when clause that included the loop counter made the descriptive exception at the bottom of the retry loop unreachable.

Behavior change worth reading

TrackedSession now completes only when all conditions are satisfied, not the first (#​3824). This is a public testing API. A tracked session configured with several expectations previously returned as soon as any one of them was met, which means some existing tests were passing vacuously. After upgrading, such a test waits for every condition — and may now fail where it previously passed. That failure is generally revealing a real gap rather than introducing one.

Other changes

• JasperFx upgraded to 2.39.5. Beyond the block Count fix above, this carries jasperfx#​600/#​601 — the application-assembly stack walk could adopt a test-runner assembly and then scan an assembly holding none of your types — and jasperfx#​599, where DatabaseId's escaping now survives a System.Uri round trip.
• EventSubscriptionAgentFamily.DatabaseKeyOf and TenantNeutralKeyOf are now public (#​3819).

Testing and CI

No runtime behavior changes here, but this is why the fixes above became findable. The Category=Flaky exclusion list went from 12 tagged classes to zero (#​3763) — and several of those tags turned out to have been added in the very commit that introduced the feature they test, hiding working code rather than broken code. Every CI readiness gate now fails loudly instead of warning and continuing; the Kafka gate in particular was a no-op that passed in 0.0s against a broker that would not serve metadata for another 3 seconds (#​3814). The retry ledger records why a test flaked rather than only which one (#​3787), and CIAzureServiceBus was sharded three ways on measured per-class durations (#​3790).

What's Changed

• Retry docker compose up so a registry timeout does not redden main by @​jeremydmiller in Retry docker compose up so a registry timeout does not redden main JasperFx/wolverine#3807
• Oracle clear_all: clean the schema the queue tables are actually in (GH-3763) by @​jeremydmiller in Oracle clear_all: clean the schema the queue tables are actually in (GH-3763) JasperFx/wolverine#3808
• Bug_2518: stop asserting exclusivity on the lock every migration takes (GH-3763) by @​jeremydmiller in Bug_2518: stop asserting exclusivity on the lock every migration takes (GH-3763) JasperFx/wolverine#3809
• Retry ledger: record WHY a flaky test failed, not just which one (GH-3787) by @​jeremydmiller in Retry ledger: record WHY a flaky test failed, not just which one (GH-3787) JasperFx/wolverine#3810
• Retry ledger: record the failing attempt's stack, not just its message (GH-3763) by @​jeremydmiller in Retry ledger: record the failing attempt's stack, not just its message (GH-3763) JasperFx/wolverine#3811
• Record the MQTT Broken pipe flake as accepted retry debt (GH-3763) by @​jeremydmiller in Record the MQTT Broken pipe flake as accepted retry debt (GH-3763) JasperFx/wolverine#3812
• Make every readiness gate fatal, and pin the images that still rolled (GH-3763) by @​jeremydmiller in Make every readiness gate fatal, and pin the images that still rolled (GH-3763) JasperFx/wolverine#3813
• Shard CIAzureServiceBus three ways on measured per-class durations (GH-3790) by @​jeremydmiller in Shard CIAzureServiceBus three ways on measured per-class durations (GH-3790) JasperFx/wolverine#3818
• Fix two test-side races behind the CISqlServer retries (GH-3821) by @​jeremydmiller in Fix two test-side races behind the CISqlServer retries (GH-3821) JasperFx/wolverine#3822
• Fix the Oracle queue Uri identity round-trip, and finish GH-3808 (GH-3820) by @​jeremydmiller in Fix the Oracle queue Uri identity round-trip, and finish GH-3808 (GH-3820) JasperFx/wolverine#3823
• Complete a tracked session only when ALL conditions are satisfied (GH-3824) by @​jeremydmiller in Complete a tracked session only when ALL conditions are satisfied (GH-3824) JasperFx/wolverine#3828
• Make EventSubscriptionAgentFamily.DatabaseKeyOf and TenantNeutralKeyOf public (GH-3819) by @​jeremydmiller in Make EventSubscriptionAgentFamily.DatabaseKeyOf and TenantNeutralKeyOf public (GH-3819) JasperFx/wolverine#3829
• Assert on the queue name, not the endpoint name, and untag Bug_2307 (GH-3827) by @​jeremydmiller in Assert on the queue name, not the endpoint name, and untag Bug_2307 (GH-3827) JasperFx/wolverine#3830
• Back-pressure observability: a latched listener says so, and block errors reach real logging by @​jeremydmiller in Back-pressure observability: a latched listener says so, and block errors reach real logging JasperFx/wolverine#3831
• Use inline senders on the tenanted Azure Service Bus path (GH-3826) by @​jeremydmiller in Use inline senders on the tenanted Azure Service Bus path (GH-3826) JasperFx/wolverine#3833
  ... (truncated)

6.24.5

Note: 6.24.4 shipped on NuGet without a GitHub release, so these notes cover everything since V6.24.3.

Highlights

Multi-database projection & subscription assignment got a major reliability pass. For sharded event stores, Wolverine assigns the agents for projections and subscriptions in groups by database — so connection pools scale with the number of databases rather than nodes × databases:

• A blue/green rollout carrying a projection version bump no longer assigns the new version's agents to nodes that cannot build them — previously the new version could never start anywhere for the whole rollout (#​3792, thanks @​erdtsieck). A split database now costs exactly one owner per version.
• Database affinity is now a property of the database across agent families (#​3785): a shard database's durability agent follows that database's projection agents onto the same node, so the database attracts one node's connection pool instead of two. Measured on a 512-database production cluster, 73% of databases were split across two nodes, wasting ~425 connection slots. Expect a one-time wave of durability-agent reassignments on first deploy as an existing cluster converges.
• The settled assignment state is now pinned as a fixed point — re-evaluating a converged cluster moves nothing — and a new deterministic simulation drives the real leader evaluation through the exact deploy shape of GH-3753: slow agent starts and a blue/green capability split at once.

Durable outbox to SNS/SQS FIFO destinations is fixed (#​3793): EnvelopeSerializer never round-tripped Envelope.DeduplicationId, so any envelope recovered from durable storage after an outage was re-sent without MessageDeduplicationId and rejected deterministically by a FIFO destination without content-based deduplication — retrying forever or dead-lettering. Also fixed alongside it: the circuit-resume ping could never reach a FIFO destination (a latched sender could never unlatch), and SNS sent MessageDeduplicationId to standard topics, which AWS rejects. The same fix is merged to the 5.x maintenance branch and will ship in the next 5.40.x release for .NET 8 users.

Balanced-mode host shutdown no longer hangs (#​3781): stopping a node while agent commands were queued could pay a full agent-batch reply window per queued command — measured at 17+ minutes. Now ~2 minutes on the same reproduction.

Azure Service Bus conventional routing sanitizes entity names (#​3786): a handler for an array message type (e.g. Handle(Foo[])) produced an illegal ASB entity name that broke broker startup for the whole assembly, and the real reason was lost. Names are sanitized and failures now carry the offending name.

What's Changed

• Never adopt a test-runner assembly as the application assembly (GH-3776) by @​jeremydmiller in Never adopt a test-runner assembly as the application assembly (GH-3776) JasperFx/wolverine#3777
• CI/testing sweep: compliance assertion scoping, Marten segmentation, dispose leaks by @​jeremydmiller in CI/testing sweep: compliance assertion scoping, Marten segmentation, dispose leaks JasperFx/wolverine#3775
• GH-3779: a dev-scale reproduction of slow agent starts, and the first flaky-tag burn-down (GH-3763) by @​jeremydmiller in GH-3779: a dev-scale reproduction of slow agent starts, and the first flaky-tag burn-down (GH-3763) JasperFx/wolverine#3780
• Stop Balanced-mode host shutdown paying a full agent reply window (GH-3781) by @​jeremydmiller in Stop Balanced-mode host shutdown paying a full agent reply window (GH-3781) JasperFx/wolverine#3782
• Wait for the ASB emulator's management api, and pin the image by @​jeremydmiller in Wait for the ASB emulator's management api, and pin the image JasperFx/wolverine#3783
• Restore 32 Azure Service Bus tests, re-tag 11 that are genuinely broken (GH-3763, GH-3786) by @​jeremydmiller in Restore 32 Azure Service Bus tests, re-tag 11 that are genuinely broken (GH-3763, GH-3786) JasperFx/wolverine#3784
• Report what every CI job spends of its retry budget (GH-3787) by @​jeremydmiller in Report what every CI job spends of its retry budget (GH-3787) JasperFx/wolverine#3788
• Sanitize Azure Service Bus entity names, and stop losing the reason (GH-3786) by @​jeremydmiller in Sanitize Azure Service Bus entity names, and stop losing the reason (GH-3786) JasperFx/wolverine#3789
• Point the AWS tests at LocalStack, and fix the SQS name limit they were hiding (GH-3763) by @​jeremydmiller in Point the AWS tests at LocalStack, and fix the SQS name limit they were hiding (GH-3763) JasperFx/wolverine#3791
• Restore the Kafka tests the Flaky tag was hiding (GH-3763) by @​jeremydmiller in Restore the Kafka tests the Flaky tag was hiding (GH-3763) JasperFx/wolverine#3794
• Stop the RabbitMQ tests colliding on shared broker names (GH-3763) by @​jeremydmiller in Stop the RabbitMQ tests colliding on shared broker names (GH-3763) JasperFx/wolverine#3795
• Restore 55 Pulsar tests and skip only the four behaviours that are missing (GH-3763) by @​jeremydmiller in Restore 55 Pulsar tests and skip only the four behaviours that are missing (GH-3763) JasperFx/wolverine#3798
• Fix DistributeByGroupAffinity assigning a bumped projection version to nodes that cannot build it by @​erdtsieck in Fix DistributeByGroupAffinity assigning a bumped projection version to nodes that cannot build it JasperFx/wolverine#3792
• Round-trip Envelope.DeduplicationId, and let a ping reach a FIFO destination (GH-3793) by @​jeremydmiller in Round-trip Envelope.DeduplicationId, and let a ping reach a FIFO destination (GH-3793) JasperFx/wolverine#3801
• Pin the group-affinity invariants GH-3792 relies on, and simulate a version bump with slow starts by @​jeremydmiller in Pin the group-affinity invariants GH-3792 relies on, and simulate a version bump with slow starts JasperFx/wolverine#3804
• Make database affinity a property of the database across agent families (GH-3785) by @​jeremydmiller in Make database affinity a property of the database across agent families (GH-3785) JasperFx/wolverine#3805
• RavenDb and CosmosDb dead-letter readers survive an unreadable body (GH-3773)
• Completion continuations honor the executor's metrics-silent tracker (GH-3774)

Full Changelog: JasperFx/wolverine@V6.24.3...V6.24.5

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)