LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: xathras

Hi,

We have a graph that whenever we run a composite node gives the following message:

"There were validation errors on some nodes. Do you want to continue executing the remaining nodes anyway" Option Yes or No.
The interest thing is the whole composite node runs and every single node works fine.

How do i track what is causing this?

Regards
Wayne

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Tim Meagher

When you receive this error, click No.
Then, the composite should display an error message when you hover over it.
You should be able to tell from the error message what the problem is.

If you don't see such a message, then you are likely running into a small corner case where these errors are not displayed on the composite, and the sub-nodes within the composite can all run.
This can occur if the composite declares parameters, and has them set to have a Validator (e.g. "Not Blank").
If such a parameter is not set, but is never actually referenced within nodes contained within the composite - or is referenced in such a way that it is never actually required (e.g. using the {{^Param=default^}} notation), then it can be that the composite node reports a validation error, as the validation is defined on the composite.
Since all of the sub-nodes do not require this parameter, they will execute successfully and there will be no error at the end of execution.
This is a minor issue with the way that composites & parameter validators interact and has been raised as issue # 3543 within our bug tracking system.

Tim.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: xathras

Hi Tim,

Thanks for the reply, I did as per your suggestion and still didn't get the detail. However, as per my previous message the nodes run perfectly fine. Looks like I am hitting this minor bug you've mentioned.
Its not a biggy, everything runs perfectly. I just wanted to get a better understanding of why that happens.

Thanks for your time in posting back.

Regards
Wayne

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: stonysmith

Open the composite, and run the nodes one at a time left-to-right.
That may help you identify which one has the issue.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: xathras

Hi,

Just wanted to post back as a follow up and say thank you. After trying that method, I was able to find no matter what node I ran I get that issue, or if I added new nodes. I got digging further and found a composite parameter being flagged at default but the default option was blank. When I set that to false, it worked perfectly fine.

I'm just tracing throughout the code to see what that specific parameter is being used for in the code.

Again thank you for your feedback

Wayne

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Tim Meagher

For the parameter in question, can you do the following:
Go into the composite node where the parameter is declared
Click on Declare Parameters
Find the declaration of the parameter in question
Check if it has a Validator set.
If so, unset the Validator.

Try & re-run the node.
If the node now completes without errors, it looks like there was probably just a validator set on the composite on a boolean parameter that wasn't required.
This is the corner case I mentioned previously.

Regards,
Tim.