As we are transitioning from OpenPype (or even converting scenes from all the way back from Avalon) we're facing issues with the scenes after the conversion if there's any trace of a detected container in the scene with an OpenPype or Avalon representation id.
When this occurs the Scene Inventory will remain empty and show no logged errors whatsoever.
There seems to be an invalid id check in the code here - but apparently it doesn't do what it should?
Note that the issue itself goes beyond just the Scene Inventory in certain validation plug-ins or alike where a query is made to the ayon_api with these invalid ids where it fails on the Graph QL queries because it disallows the invalid ids. An approach we could take is to have Ayon API filter those out with the uuid check.
Expected Behavior:
It should allow to list invalid containers and if any issue arises like this it should provide a logged stack trace as well.
Version
1.0.0
What platform you are running on?
Windows
Steps To Reproduce:
To reproduce:
Load a published product into a host integration
On the container manipulate the data and remove some characters from representation id.
Load another published product
Open the scene inventory
Nothing shows, both the broken and the normal container are not listed.
Are there any labels you wish to add?
[X] I have added the relevant labels to the bug report.
Relevant log output:
No response
Additional context:
I wish there was some log or error output to share - but there's literally no output whatsoever when this fails.
Is there an existing issue for this?
Current Behavior:
As we are transitioning from OpenPype (or even converting scenes from all the way back from Avalon) we're facing issues with the scenes after the conversion if there's any trace of a detected container in the scene with an OpenPype or Avalon representation id.
When this occurs the Scene Inventory will remain empty and show no logged errors whatsoever.
There seems to be an invalid id check in the code here - but apparently it doesn't do what it should?
Note that the issue itself goes beyond just the Scene Inventory in certain validation plug-ins or alike where a query is made to the
ayon_apiwith these invalid ids where it fails on the Graph QL queries because it disallows the invalid ids. An approach we could take is to have Ayon API filter those out with the uuid check.Expected Behavior:
It should allow to list invalid containers and if any issue arises like this it should provide a logged stack trace as well.
Version
1.0.0
What platform you are running on?
Windows
Steps To Reproduce:
To reproduce:
Are there any labels you wish to add?
Relevant log output:
No response
Additional context:
I wish there was some log or error output to share - but there's literally no output whatsoever when this fails.