Luís Garcês

Just adding up, this behavior is exclusive to in-memory data source implementation, perhaps the solution can be thought of as part of in-memory implementation (non-binding, just an observation).

Proposed solution: 1. Move the handling of the `next` middleware to `InvokeAsync`. 2. Add an additional filter resource segment to `StaticFileMiddleware` configuration. ```csharp private async Task ExecuteHandlersAsync(HttpContext httpContext) { var...

Hi @dtkujawski, Thank you for reaching out and for your suggestion. We have discussed your request internally and we'll assess the feasibility of it as soon as we find the...

@Daniel-C-Dias wasn't your intention to create this issue on KafkaFlow Retry extension repository?

We have discussed this internally, and we want to: - Review the verbosity of logs already done. - Add additional logs where it makes sense.

Hi @seruminar, From your description, it seems to be a bug, but we'll check this out and get back to you with further details. Can you provide us with a...

Hi @adambajguz, First of all, thank you for your feature request. We find that the usage of RavenDB as a storage provider is a valid use case and we agree...

I will work on a proposal comprising a database schema (high-level) to address this need.

Adding screenshot.  Let me also suggest resolving this with a task continuation that verifies if this task has failed, and takes proper action after (e.g. emit an error log...

Beta package generated: https://www.nuget.org/packages/Rules.Framework.Rql/3.0.0-beta.1