First, i was under the impression, that the generic input is the culprit, which was the reason to create the genericAdaptive.vl testpatch. Since this one works as expected, the issue must be something else.
Hey. Finally had a look at this one. I managed to get into a crash by setting up a XML binding to a Spread<Float32> - but it triggered a slightly different crash. It didn’t respect a value type constraint on a type parameter when looking up candidates for in this case TryParse. After fixing (in upcoming 7.2 preview) and supplying an implementation for TryParse on spreads it worked correctly.
So my question: to what channel did you try to bind? What type did that channel have? Don’t see that in your provided patches.
i finally came back to this and i think i found a misbehavior, because i still see sometimes my adaptive nodes not being picked up and after some hunting i found it might be related to generics.
please see the attached screenshot. on the left you see the adaptive ToString working just fine when connected to the SetXpathValue node. But when both are wrapped in a generic patch as you can see in the middle, i get this error message.
