Steven van Beelen

Removed milestone 4.6.0 from this issue, as it's unlikely that we'll introduce it as part of the 4.6.0 release.

I agree with the decision you and the team made, @magnusdurr. This seems serious enough to share, even though you're not capable to replicate the scenario. I don't see anything...

Thanks for the update above, @magnusdurr. That provides some guidance, although not necessarily a conclusion to how it happened. We have a hunch right now, by the way. But, let...

With that said, I do have another question for you. Did you notice duplicate event handling **for all the events** or for a **subset of** the events?

I hope the answer is no, but I'm going to ask it regardless: have you seen the described predicament again, @magnusdurr? And if so, with which version of AF? Is...

I am closing this issue due to inactivity. If you have any updates on the matter, @magnusdurr (or others encountering this predicament), be sure to share those with us.

The position can be two things in this case. Either (1) the position of the last event appended in that aggregate's event stream or (2) the position of the last...

This is a nice addition to the framework, @jasperfect. Note that this isn't part of Axon's implementation at the moment. Hence, marking it as a bug is incorrect; you should've...

By the way, as a workaround right now, you can simply do a `return` in your `@CommandHandler` annotated method to return the aggregate identifier of the newly created aggregate.

As you can see, the prioritization on this is rather low on our end. Simply because doing it yourself is very straightforward. However, as this is an open-source project, any...