You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rule if (propertyValue != null) {
propertyValue.causes := assignments.reasonRefs.distinct.copy;
}
rule if (propertyValue != null) {
propertyValue.result := derivedValue;
}
there seem to be other solutions like changing the order of the assignments, adding .toList after the copy or adding some tracing of assignments.reasonRefs.distinct.copy in a local variable.
We discovered this in a private repo (Osteoporose), see revision e39faec67a5558fd3076b66ed2a2aba8e4a8b10c.
The above change in cdm (also private) is in 59848d85f759daa0c83500b95bbf6ebcb51a5c1f.
The text was updated successfully, but these errors were encountered:
The following rule triggers it:
the following change solves it:
there seem to be other solutions like changing the order of the assignments, adding
.toList
after the copy or adding some tracing ofassignments.reasonRefs.distinct.copy
in a local variable.We discovered this in a private repo (
Osteoporose
), see revisione39faec67a5558fd3076b66ed2a2aba8e4a8b10c
.The above change in
cdm
(also private) is in59848d85f759daa0c83500b95bbf6ebcb51a5c1f
.The text was updated successfully, but these errors were encountered: