Alexey Zimarev

That's what I meant. So, basically, the `+ 1` in the context construction just brings the sequencing to zero-lead as it's the default behaviour for Eventuous. It's confusing when you...

With #164 presumably fixed, is this one still relevant?

Yeah, it's a bit too late as changing the sequence would produce hidden consequences of skipping one event. I haven't been able to document both SQL stores yet, will keep...

Can you post the checkpoint query, as it's hard to understand what `NR` fields mean and the query is not fully visible.

One more thing, could you post your bootstrap code? The subscription configuration part is essential, and where you tell the application to use the particular checkpoint store.

And one more thing: > if only a single Save is missed the Checkpoint can never again be updated by the same running application That's by design, as the expectation...

Commits don't happen when the commit handler cannot get a gapless sequence of checkpoints. Each event received by a subscription gets its own monotonically increasing sequence number. When events are...

Here comes some new diags: https://github.com/Eventuous/eventuous/pull/172

All the preview versions are on MyGet. It's described in the readme.

It seems really weird as it looks the same to me ``` Last commit position 10243:10243 is behind latest position 10243:10243 ``` Seems like a bug, the same event was...