## Two overlapping txns.
## Two writes to the same key should be rejected with a LockConflictError.

run error
with t=A
  txn_begin  ts=33
  put   k=a v=xyz
with t=B
  txn_begin  ts=44
  put   k=a v=zzz
----
put: lock acquisition = {a id=00000001 key=/Min iso=Serializable pri=0.00000000 epo=0 ts=33.000000000,0 min=0,0 seq=0 Replicated Intent []}
>> at end:
txn: "B" meta={id=00000002 key=/Min iso=Serializable pri=0.00000000 epo=0 ts=44.000000000,0 min=0,0 seq=0} lock=true stat=PENDING rts=44.000000000,0 wto=false gul=0,0
meta: "a"/0,0 -> txn={id=00000001 key=/Min iso=Serializable pri=0.00000000 epo=0 ts=33.000000000,0 min=0,0 seq=0} ts=33.000000000,0 del=false klen=12 vlen=8 mergeTs=<nil> txnDidNotUpdateMeta=true
data: "a"/33.000000000,0 -> /BYTES/xyz
error: (*kvpb.LockConflictError:) conflicting locks on "a"

## It's possible to observe the intent with an inconsistent read.

run ok
with t=B
  get k=a inconsistent
----
get: "a" -> intent {id=00000001 key=/Min iso=Serializable pri=0.00000000 epo=0 ts=33.000000000,0 min=0,0 seq=0}
get: "a" -> <no data>
