You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Houdini Nodes can include different type of parameters and some of them like ramp breaks the instances collection as copy.deepcopy fails.
Here's some bug report when it fails
Yes - for the containers we already did this, but we should also for creators. (It may also make them faster!)
So we would be getting way more explicit about the attributes we're expecting. However, currently those are quite a lot already - especially with backwards compatibility:
I'm not entirely sure whether we need to read the legacy attributes or whether we're already reading those explicitly separately. But I suspect we may need to keep them in the read for creators logic for the time being? Note that we should avoid changing read function to hardcode those values - but instead implement the limited list to read in the Creators (or wherever we're querying that. The read method should stay in tact.
Is there an existing issue for this?
Description
Current Behavior
ayon_houdini.api.lib.read should get extra AYON parameters.
Houdini Nodes can include different type of parameters and some of them like
ramp
breaks the instances collection as copy.deepcopy fails.Here's some bug report when it fails
cannot pickle 'SwigPyObject' object
when checking the instance data, it shown something like
Expected Behavior
read
function should only get AYON parametersSteps To Reproduce:
Additional context:
Version
latest everything
What platform were you running when you found the bug?
Windows
You can also provide any additional information relevant to the issue.
Relevant log output:
The text was updated successfully, but these errors were encountered: