Hi,

I have a question regarding backup order of *.chk files themselves.

If I understand various bits of info from documentation, Github issues and Google Groups, content of chaser.chk is pointer to position (in chunk files "continuum") reached by chaser process, while writer.chk is pointer to position reached by writer process. Chaser process should always be behind the writer (or at the sam

Description

I'm on 3.5.1 and it seems that things are still initialized before APP_INITIALIZER.
Not sure if I'm missing something or if I don't completely understand what this issue's resolution should be?

This is my use case:
I need to initialize Ngxs through a library module that either is imported or not in the apps (monorepo structure)
And I couldn’t find a way to initialize it pr

We use http_server as input and http_client as one of outputs (for a part of message batch). In case when there is some error coming from http_client, benthos starts to retry this error message indefinitely (#415). However most significant, is that it stops accepting other, normal messages.

Here is the log when I first try to send message which causes http_client to get 500 error, and

Currently, you are not able to use middleware per handler in "clean way" (you can still manually wrap the handler function, or have separated router).

It would be nice to be able to add middleware per handler.

As a good reference point, you can use chi router: https://github.com/go-chi/chi

Currently understanding what's going on when using the first time the framework is quite complex (at least from my point of view ;)).

Would it be possible to add some debug/trace logging during the configuration/bootstrap phase of Axon in order to get insight on what was configured and instantiated.

For example I added a TrackingEventProcessor in my configuration but it was never started

Just highlighting this in case you're interested, I took a fork of @dennisfabri racetimes example and extended it to run with Azure Functions and then extended again to publish to Azure EventGrid as a new extension inspired by the RabbitMQ example. Might be of interest to others.

https://github.com/craignicol/Eventflow.Example.Racetimes/tree/feature/event-grid-as-extension

To help onboard new users it would be useful to describe the main building blocks required to start using Commanded and configure an event store.

• Commanded.Application - explain what it is, and that it differs from an OTP application.
• Event store - adapter configuration and event store definition (e.g. define EventStore module).

I figured out that node-sass dependency mentioned in web package is obsolete now.

I tried to change it to

"devDependencies": {
"@vue/cli-plugin-babel": "^3.0.0-rc.10",
"@vue/cli-plugin-eslint": "^3.0.0-rc.10",
"@vue/cli-service": "^3.0.0-rc.10",
"node-sass": "^4.14.0",
"sass-loader": "^7.0.3",
"vue-template-compiler": "^2.5.16"
},

then web-vue built s

In case there is a projection with no handlers we'd still traverse given streams only to produce no result. It's an unusual case but still we're able to produce "no result" much faster.

Can anyone give flow diagram which classes get hit in sequence from start to end in eventhorizon.
It will be great help I am waiting for this no documentation so far available on net.

What is this feature about?

With tailwind, we have created a standard for how to send commands, wait for events and query read models. We should describe this in the documentation, since from time to time people are interested in how to access a wolkenkit application directly, i.e. without using the client SDK.

What needs to be done to implement this feature?

• Add a page on t

I tried to search for Prooph Add Metadata and got this page as 1st result: http://getprooph.org/docs/html/event-store/event_store.html

I think the right/updated documentation in different host: http://docs.getprooph.org/event-store/event_store_plugins.html#3-3-4

I think it's important to have results in google to redirect to right documentation :)

Thanks

https://github.com/defunctzombie/zuul is unmaintainced.
We want to replace zuul to another testing library.