Resolve: Update container errors

[tokejepsen]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior:

Updating a container in the manager errors with:

Traceback (most recent call last):
  File "C:\Users\tokejepsen\ayon-core\client\ayon_core\tools\sceneinventory\view.py", line 236, in <lambda>
    lambda: self._update_containers(items, version=-1)
  File "C:\Users\tokejepsen\ayon-core\client\ayon_core\tools\sceneinventory\view.py", line 819, in _update_containers
    update_container(item, item_version)
  File "C:\Users\tokejepsen\ayon-core\client\ayon_core\pipeline\load\utils.py", line 517, in update_container
    return Loader().update(container, context)
  File "C:\Users\tokejepsen\ayon-core\client\ayon_core\hosts\resolve\plugins\load\load_clip.py", line 82, in update
    self.set_item_color(timeline_item, version=context["version"])
  File "C:\Users\tokejepsen\ayon-core\client\ayon_core\hosts\resolve\plugins\load\load_clip.py", line 130, in set_item_color
    version["parent"],
KeyError: 'parent'

Expected Behavior:

No response

Version

1.0.0

What platform you are running on?

Windows

Steps To Reproduce:

1. Load a clip (EXR) into a timeline in Resolve.
2. Switch version in the Manager.

Are there any labels you wish to add?

• I have added the relevant labels to the bug report.

Relevant log output:

No response

Additional context:

No response

[BigRoy]

Shouldn't parent key always be present on version data?

Unless the entity was queried with fields argument so that it excludes parent, but I believe the context being used here should contain that since those are the queries of the representation contexts?

---

Edit: it only happens on update?

If so, then it's likely due to this PR #130

[BigRoy]

The issue is here

Those queries filter fields but we want to pass the full context to the Loader.update calls.

Bug was introduced with #130 indeed.

[jakubjezek001]

hey @tokejepsen I believe this had been fixed already. Can you try again please?

[tokejepsen]

hey @tokejepsen I believe this had been fixed already. Can you try again please?

Nice, resolved!