wolverine
wolverine copied to clipboard
JasperFx
Next Generation .NET Command and Message Bus
This PR fixes #766. It modifies the `EmptyBody204Policy` policy to check if the `HttpResponse` status code is the default in addition to checking `HasStarted`. Only if both conditions are met...
**Describe the bug** My application uses Wolverine both to publish and subscribe messages using Kafka transport and MSSQL persistence. The problem is with enabling/disabling outbox/inbox. To test all scenarios I've...
* WIP This PR is to adds support for Amazon Simple Notification Service (SNS). Mentioned in the issue #58 So far my plan is to create a separate transport for...
**Describe the bug** Kafka transport automatically creates declared topics even if `AutoProvision()` was not called during configuration, i.e. `AutoProvision` flag is set to false. I've tested this on the latest...
**Describe the bug** The use of ISideEffect does not work in the current version 3.11. When starting the application, the exception “InvalidSideEffectException” occurs although the side effect class has public...
When a logger isn't passed Weasel falls back to a console logger which can't be controlled externally. We could expose the `IMigrationLogger` on the `DatabaseBase` in weasel and re-use here...
**Describe the bug** When using Kafka / Redpanda as external transport listener that accepts JSON data with durable inbox storage, whenever a producer produces a non-JSON message, the consumer will...
Using Wolverine v 3.8.0 Using Marten 3.8.0 Observation: Saga TimeOutMessages gets scheduled three times if the application is back up after the stored TimeOutMessage timeout is up it causes two...
**Is your feature request related to a problem? Please describe.** Wolverine does not accept request bodies in GET endpoints, only [primitive types as query parameters](https://wolverine.netlify.app/guide/http/querystring.html). Accepting request bodies in GET...
