Arithmetic Constraints ignore Feature-Clones

[FAuersw]

Hi, i just encountered a situation where constraints on attributes are only checked on the first instance of a feature.

features
	A cardinality [1..2]
		optional
			B {v 1}
			C {v 1}

constraints
	B.v + C.v == 1
	B & C

Here the configuration {A1,B1,A2,B2,C2} without C1 is valid but {A1,B1,C1,A2,B2} without C2 is not. Any configuration without A1 seems to be unsat too.
I suspect the scoping of regular features and attributes to be not the same. I would expect this model to be void unless attribute values are changed.

[SundermannC]

Hi @FAuersw,
thanks a lot for your report and taking time to find an explanation! :)
This indeed appears to be a bug. I would also share your expectation on the behavior that this feature model should be void with the set attribute values.