Rafał Łasocha

@leifg Yes, definitely, but there are a few different paths we can take from the current state of the spike -- we need to do slightly more research and decide...

Also, there's no distinction between "event not loaded yet" and "event not found", so sporadically, user may see "Event not found" information for a fraction of second when the event...

For now it's probably not yet possible to successfully run it, because of https://github.com/oracle/truffleruby/issues/1400 . But someone can try :)

I like that :+1:

To solve the issue, we could have a global `subscription_counter`, one integer, stored per event store instance. That counter would be incremented with each subscribed handler. ``` # Current value...

I will try to elaborate on that later, but just for the sake of leaving some information: We did have encounter a situation in which lot of savepoints was serious...

``` # - repository: # - dispatcher: # - mapper: # ```

What would you say about something like this? ``` # ```

Just to recap: 1) in the beginning we had big blob of text, which had all information, but was only useful when using some `find` tools. Also it was just...

I'm not sure what information we could retrieve, having in consideration that we would like to have some useful data from maintainers perspective and don't loose trust by executing doubtful...