[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [tlaplus] Why does adding a new step collapse my model to a single state?

This got me thinking what could be different between our environments, and led me to a discovery:

This "collapsing" only happens when either (or both) VoidRedundantAuths or EventualCapture are added to the model as a temporal property to check. (I also have DistinctIds and NoDoubleCapture as invariants, they do not cause the issue.) I am suspicious of the `Success ~>` pattern I have used in those, it feels a bit weird, but am not sure why yet.

I'm using toolbox on Ubuntu 18.10. Here is a link to a zip of my payments.toolbox folder: https://drive.google.com/file/d/1qASlY0euOqg7VCd2QFKD68y86ieLICwf/view?usp=sharing

Thank you both for taking the time to assist!

On Saturday, 30 March 2019 01:41:28 UTC+11, Markus Alexander Kuppe wrote:
On 29.03.19 00:44, Stephan Merz wrote:
> I tried to reproduce your problem. Copying the module from your GitHub site and commenting out the second call of HandleRequest, TLC indeed generates 383 distinct states. With the second call, it generates 1419 distinct states (still for 3 data centers). I haven't tried to understand what the specification is about, but I'm afraid I cannot help you any further at this point.

Hi Xavier,

it's the same here, the modified spec has 1419 states.

If TLC reproducibly finds only a single state on your machine, please
privately share your spec, model, as well as environment information
with me and I will look into it.


You received this message because you are subscribed to the Google Groups "tlaplus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tlaplus+unsubscribe@xxxxxxxxxxxxxxxx.
To post to this group, send email to tlaplus@xxxxxxxxxxxxxxxx.
Visit this group at https://groups.google.com/group/tlaplus.
For more options, visit https://groups.google.com/d/optout.