Jack Vanlightly

> Here has a mail about this: http://mail-archives.apache.org/mod_mbox/bookkeeper-dev/202111.mbox/browser Considering that data loss is an outcome of this operation, I think that should be clearly communicated here. When this data loss...

@1559924775 thanks for spotting this. However I think the proposed solution isn't quite right. I think there should be a cleaner solution without resorting to reflection. For example, one solution...

Yes, I will review it and give feedback.

@BinyuHuang-nju I have run it a couple of times and hit some invariant violations, such as LocalPrimaryOrder and Integrity. I have not taken the time to understand the spec or...

I left the new version running on my workstation overnight with Servers {s1,s1} symmetrical and Values {v1,v2} symmetrical and no violations happened. It was still running this morning after 16...

@BinyuHuang-nju with 3 servers and 1 value it now hits all actions. It's been running for 20 hours and reached a diameter of 22 with over 17 trillion states, 2...

@BinyuHuang-nju good work getting it to reach a higher diameter, that improves our confidence in the spec. I will start digging into the functioning of the spec itself and provide...

From my perspective: 1. Implement the minimum required, in order to keep thing simpler and reduce the state space. If the only point of the PING message is to act...

I have started looking at the new version. One thing I have done is add a TypeOK invariant checking that the types of all variables are correct in all states....

I have finished my review of the spec against the code and I do not find any problems in terms of correctness. There are however, a number of suggestions. -...