[dependabot]

Updated WolverineFx from 6.55.1 to 6.57.0.

Release notes

Sourced from WolverineFx's releases.

6.57.0

New

• GH-5244 (#​5272): NServiceBus interop now supports XML. Many NServiceBus systems still use the NServiceBus XmlSerializer, and they no longer have to switch to JSON before a migration to Wolverine can start. Every NServiceBus interop endpoint (Rabbit MQ, Azure Service Bus, Amazon SQS and SNS, and the SQL Server and PostgreSQL NServiceBus transports) now reads both JSON and XML, choosing per message from the NServiceBus.ContentType header. To send XML, use the new NServiceBusXmlSerializer: .UseNServiceBusInterop().DefaultSerializer(new NServiceBusXmlSerializer()). Because one endpoint reads both formats, NServiceBus endpoints can also move from XML to JSON gradually. See XML Serialization with NServiceBus.
• #​5268 (thanks @​lahma) and #​5273: A durable listener now gives a message from a non-Wolverine producer, which has no Wolverine id, a stable envelope id derived from the broker's own identity for that message. A redelivery is then deduplicated by the durable inbox instead of being handled twice. This covers Kafka (topic, partition and offset), NATS JetStream, Pulsar, Redis Streams, Amazon SQS and GCP Pub/Sub pull subscriptions. On SQS and Pub/Sub it applies in every endpoint mode. #​5273 also makes raw JSON work on durable SQS listeners. A duplicate the durable inbox refuses is now logged at Information instead of as an error.
• GH-5260 (#​5261): New opt-in WolverineHttpOptions.RejectUnparseableHeaderValues answers 400 with ProblemDetails when a [FromHeader] value can't be parsed.

Fixes

• GH-5244 (#​5272): NServiceBus replies to Wolverine over Rabbit MQ now go to the queue marked UseForReplies(). Wolverine used to give NServiceBus its own wolverine.response.{guid} system queue as the reply address, which NServiceBus can't reach, so every reply ended up in NServiceBus's error queue.
• GH-5247 (#​5248): DurabilityAgent.StopAsync() now cancels its in-flight durability command and waits for it to finish. Before, a command still running at shutdown could outlive the host and fail against a disposed data source.
• GH-5253 (#​5256, thanks @​thomhurst): A leadership lock acquisition cancelled by node shutdown is no longer logged as an error.
• GH-5254 (#​5265): Shutdown now waits for handlers still running on a buffered local queue.
• GH-5257 (#​5266): Stopping a listener now interrupts an inline retry cooldown instead of waiting it out, and the retry doesn't run after the stop.
• GH-5262 (#​5263): Lightweight EF Core handlers now collect domain events before their save, so the events are published atomically with it.
• #​5245 (thanks @​ahyousif): Managed EF Core tenancy combined with WithDbContextAbstraction now reuses the tenant DbContext, so repository writes, the save and outbox enrollment all use one context. This could previously fail code generation.
• #​5250 (thanks @​johnkaram02): A request that repeats a [FromHeader] header binds the comma-joined values instead of answering 500.
• #​5252 (thanks @​johnkaram02) and #​5259: Additional error actions such as AndPauseProcessing() chained after ScheduleRetryIndefinitely() / RequeueIndefinitely() now apply, including to the open-ended attempts after the listed delays.

Dependencies

• JasperFx 2.96.1 and JasperFx.RuntimeCompiler 5.0.1 (#​5258)
• Weasel 9.47.1 (#​5269)

Docs and build

• The Best Practices guide is rewritten (#​5270).
• New docs for stable envelope ids from non-Wolverine producers, and for deduplicating CloudEvents (#​5273).
• ./build.sh LocalGate runs every CI suite on one machine (GH-5125, #​5246). The CI suites are rebalanced to stay under the 20 minute job limit (#​5267), and the scaffold tests now pass on Windows (GH-5255, #​5264).

6.56.0

New

• GH-5238 (#​5242): opts.UseHttpTransport() registers the HTTP transport inside UseWolverine(). http/https URIs then resolve in ListenForMessagesFrom(), PublishMessage<T>().To(uri), and runtime EndpointFor() / ToDestination(). Before this, the transport was only registered by ToHttpEndpoint(), and any other http URI failed with Unknown Transport scheme 'http'. /_wolverine/invoke now answers 415 instead of 500 for a content type with no registered serializer.

Fixes

• GH-5235 (#​5239): Host shutdown now stops the durability metrics sweeper and waits for any query it has in flight before stores are disposed. Removing a durability agent also waits for its in-flight query. A metrics query could previously outlive IHost.StopAsync() and throw ObjectDisposedException against a disposed NpgsqlDataSource.
• GH-5236 (#​5240): A Kafka listener with a durable inbox no longer crashes the process with a stack overflow when the inbox database is unavailable. DeferAsync() used to call back into the receiver inline, so the failed inbox write and the defer recursed. A deferred Kafka envelope now goes back to the receiver on its own task after a short pause, and only while the listener is running. After a stop or inbox-recovery pause, its uncommitted offset brings it back. Because Kafka has no native requeue, a Requeue error policy on a Kafka endpoint now redelivers after about one second instead of immediately.
• GH-5237 (#​5241): A CloudEvents HTTP endpoint now fails a single-envelope send that the receiver rejects. It used to count the send as delivered, so a durable endpoint aimed at /_wolverine/invoke could delete an outgoing envelope that was never received. HTTP transport responses are now disposed.

Commits viewable in compare view.

Updated WolverineFx.RabbitMQ from 6.55.1 to 6.57.0.

Release notes

Sourced from WolverineFx.RabbitMQ's releases.

6.57.0

New

• GH-5244 (#​5272): NServiceBus interop now supports XML. Many NServiceBus systems still use the NServiceBus XmlSerializer, and they no longer have to switch to JSON before a migration to Wolverine can start. Every NServiceBus interop endpoint (Rabbit MQ, Azure Service Bus, Amazon SQS and SNS, and the SQL Server and PostgreSQL NServiceBus transports) now reads both JSON and XML, choosing per message from the NServiceBus.ContentType header. To send XML, use the new NServiceBusXmlSerializer: .UseNServiceBusInterop().DefaultSerializer(new NServiceBusXmlSerializer()). Because one endpoint reads both formats, NServiceBus endpoints can also move from XML to JSON gradually. See XML Serialization with NServiceBus.
• #​5268 (thanks @​lahma) and #​5273: A durable listener now gives a message from a non-Wolverine producer, which has no Wolverine id, a stable envelope id derived from the broker's own identity for that message. A redelivery is then deduplicated by the durable inbox instead of being handled twice. This covers Kafka (topic, partition and offset), NATS JetStream, Pulsar, Redis Streams, Amazon SQS and GCP Pub/Sub pull subscriptions. On SQS and Pub/Sub it applies in every endpoint mode. #​5273 also makes raw JSON work on durable SQS listeners. A duplicate the durable inbox refuses is now logged at Information instead of as an error.
• GH-5260 (#​5261): New opt-in WolverineHttpOptions.RejectUnparseableHeaderValues answers 400 with ProblemDetails when a [FromHeader] value can't be parsed.

Fixes

• GH-5244 (#​5272): NServiceBus replies to Wolverine over Rabbit MQ now go to the queue marked UseForReplies(). Wolverine used to give NServiceBus its own wolverine.response.{guid} system queue as the reply address, which NServiceBus can't reach, so every reply ended up in NServiceBus's error queue.
• GH-5247 (#​5248): DurabilityAgent.StopAsync() now cancels its in-flight durability command and waits for it to finish. Before, a command still running at shutdown could outlive the host and fail against a disposed data source.
• GH-5253 (#​5256, thanks @​thomhurst): A leadership lock acquisition cancelled by node shutdown is no longer logged as an error.
• GH-5254 (#​5265): Shutdown now waits for handlers still running on a buffered local queue.
• GH-5257 (#​5266): Stopping a listener now interrupts an inline retry cooldown instead of waiting it out, and the retry doesn't run after the stop.
• GH-5262 (#​5263): Lightweight EF Core handlers now collect domain events before their save, so the events are published atomically with it.
• #​5245 (thanks @​ahyousif): Managed EF Core tenancy combined with WithDbContextAbstraction now reuses the tenant DbContext, so repository writes, the save and outbox enrollment all use one context. This could previously fail code generation.
• #​5250 (thanks @​johnkaram02): A request that repeats a [FromHeader] header binds the comma-joined values instead of answering 500.
• #​5252 (thanks @​johnkaram02) and #​5259: Additional error actions such as AndPauseProcessing() chained after ScheduleRetryIndefinitely() / RequeueIndefinitely() now apply, including to the open-ended attempts after the listed delays.

Dependencies

• JasperFx 2.96.1 and JasperFx.RuntimeCompiler 5.0.1 (#​5258)
• Weasel 9.47.1 (#​5269)

Docs and build

• The Best Practices guide is rewritten (#​5270).
• New docs for stable envelope ids from non-Wolverine producers, and for deduplicating CloudEvents (#​5273).
• ./build.sh LocalGate runs every CI suite on one machine (GH-5125, #​5246). The CI suites are rebalanced to stay under the 20 minute job limit (#​5267), and the scaffold tests now pass on Windows (GH-5255, #​5264).

6.56.0

New

• GH-5238 (#​5242): opts.UseHttpTransport() registers the HTTP transport inside UseWolverine(). http/https URIs then resolve in ListenForMessagesFrom(), PublishMessage<T>().To(uri), and runtime EndpointFor() / ToDestination(). Before this, the transport was only registered by ToHttpEndpoint(), and any other http URI failed with Unknown Transport scheme 'http'. /_wolverine/invoke now answers 415 instead of 500 for a content type with no registered serializer.

Fixes

• GH-5235 (#​5239): Host shutdown now stops the durability metrics sweeper and waits for any query it has in flight before stores are disposed. Removing a durability agent also waits for its in-flight query. A metrics query could previously outlive IHost.StopAsync() and throw ObjectDisposedException against a disposed NpgsqlDataSource.
• GH-5236 (#​5240): A Kafka listener with a durable inbox no longer crashes the process with a stack overflow when the inbox database is unavailable. DeferAsync() used to call back into the receiver inline, so the failed inbox write and the defer recursed. A deferred Kafka envelope now goes back to the receiver on its own task after a short pause, and only while the listener is running. After a stop or inbox-recovery pause, its uncommitted offset brings it back. Because Kafka has no native requeue, a Requeue error policy on a Kafka endpoint now redelivers after about one second instead of immediately.
• GH-5237 (#​5241): A CloudEvents HTTP endpoint now fails a single-envelope send that the receiver rejects. It used to count the send as delivered, so a durable endpoint aimed at /_wolverine/invoke could delete an outgoing envelope that was never received. HTTP transport responses are now disposed.

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)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: NosCoreIO/NosCore
• Branch: master
• File: .coderabbit.yaml
• Commit: 16bc70e
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: 4de9ae97-acb7-42e7-b730-e035e4caf3d9

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}