Closed AthenaSchulz closed 2 years ago
I guess this happened by using features of Alloy 6.0.0 (mutable state)?
Could you provide the original Alloy code leading to this error (i.e. the actual parameters of getInstances
)?
getInstances
was originally called on https://github.com/fmidue/ba-athena-schulz/blob/master/src/AD_Alloy.hs#L38 in that module, to which the corresponding alloy files concatenated in there can be found here: https://github.com/fmidue/ba-athena-schulz/tree/master/alloy/ad
Node that this problem also appeared when just using https://github.com/fmidue/ba-athena-schulz/blob/master/alloy/ad/ad_components_sig.als (with a predicate and a run
-statement attached at the end)
If you dont have access to that repo, I could send you the files you are interested in privately
The
getRawInstances
andgetRawInstancesWith
function from theLanguage.Alloy.Debug
module seems to produce ByteStrings with a "------State 0-------" line under certain circumstances, which does not seem to be handled well by theparseInstance
function (or functions likegetInstances
that use those internally).Sample output of
getRawInstances
with that issue:with which only loop, end and integers seem to be recognized by
parseInstance
.For more information see also: https://github.com/fmidue/ba-athena-schulz/issues/7