bsbds

> > The operations in a single txn should be executed sequentially. However in Xline, we donot check for conflicts inside a single txn, all commands result are based on...

cc @calvin0327 @RainbowMango

In `handle_propose` the leader need to generate the prepare result(revision) for the execution stage(beacuse the revision need to return to user in speculative execute), but this prepare result may get...

Please add more details about why the lock order could cause a timeout.

Also tracked in https://github.com/etcd-io/etcd/issues/16380

## Background We have two stage `execute` and `after_sync`, however during a multi-request txn execution of these two stage, one executing child request does not see the effect of a...

> Hello there @bsbds ! I'd like to work on this issue if that's fine by you. Thank you! Sure, assigned.

> Hey @bsbds ! I have made the necessary changes to the code. Wanted to ask if there are any more error-codes other than `CurpError::WrongClusterVersion` and `CurpError::Redirect` that need immediate...

Rebased on #705

This implementation is too complex compare to the original prefix sum version. I suggest making some modifications to the original algorithm. Here's the pseudocode. The interval representation is `[left, right)`....