Bug: Houdini: New Publisher validations unusable validation reports

[BigRoy]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior:

Since the refactor of Houdini to the new publisher the validations have become pretty unusable since they report the wrong things or just don't report any usable information at all. An artist would not know what to do in any of e.g. the following screenshots:

Or as reported here the following areas in the code:

• here an artist will just see Invalid paths found with no details on what to do, what paths they are, where they come from and what's wrong about it.
• This reports something that might not even be true since it totally disregards the logged errors below it.
• This mentions "output" even though it's for the input nodes and suffers from the same issue as above. It reports something that doesn't explain what happened. This was actually a duplicate validator, see Houdini: Fix Validate Output Node (VDB) #4819
• This, This and This just reports to look at the log output but the new publisher has nothing that redirects an artist to easily look at the log of that instance or node.

These are just a few of the plug-ins I have investigated.

Expected Behavior:

The reports should be clear for the artist. Seeing a report I should be able to understand what went wrong quickly and know what to do next.

Version

3.15.3

What platform you are running OpenPype on?

Windows

Steps To Reproduce:

1. Publish invalid content from Houdini (check the validators to see how you can best make sure they "invalidate" your scene)

Is there any more labels you wish to add?

• I have searched labels and added any

Relevant log output:

No response

Additional context:

No response

[cuID:OP-5572]

[antirotor]

Here is discussion related to this: https://community.ynput.io/t/publishing-better-error-reporting/55/4

[MustafaJafar]

You are discussing Houdini validations error reports that don't make sense

for example you mean this (which is a Houdini issue)

and you don't mean not this (which is a Publisher issue)

@BigRoy Could you tell me if I got it right ?
Becasue, if this is the case then this task is miscategorized.