Inline Randomization Issue in 0.2.4 release about pyvsc HOT 2 CLOSED

Hi @aneels3,
After a bit of digging, I was able to reproduce the problem (I wanted to ensure I had a test that would trigger this). The most immediate cause of the problem is some diagnostic code that made an incorrect assumption about the API implemented by all fields. I've corrected this issue, and will update the release version later today. So, you're correct with your fix to add a default to the 'level' parameter.
As you note, this does result in a solve failure. It's possible this results from the changes to support solve ordering. I do see that your inline constraint uses regular Python procedural if/then statements. It's possible that using these instead of constraint if/then statements (eg vsc.if_then) could cause the problem.
Do try catching the SolveFail exception and displaying it. Solve-fail diagnostics are still being developed, but sometimes they can help. Have a look at this test:

Best Regards,
Matthew

from pyvsc.

Hi @mballance
Thanks for the quick support on this issue. It's working as expected now.
closing the issue for now. If I find any issue related to this in the future, I will reopen it.

Regards,
Anil

from pyvsc.