Add context reset prompt on taskChange

[sebastianbrandhuber]

Changelog Description

This PR implements a pop-up dialog that allows users to interactively choose whether, and what, should be adapted to the new context before a context change callback - very similar to its counterpart in ayon-houdini.

Additional review information

Additional information can be found here in the issue itself:
Fix #265

Testing notes:

1. Start nuke, save a scene with the workfiles tool.
2. (Optional) Create a write instance
3. Using the workfiles tools, save this existing scene into a different context
4. A dialog shows up and lets the user choose what should be adapted to the new context.

Current limitations and unintended bahaviour:

• The product name of the instance does not get updated automatically - visible in the publish dialog.
• The node name of the instance node does not get updated
• The instance node's group children are not being renamed aswell.

[BigRoy]

Nice - very nice! Code looks very close to similar functionality in e.g. Maya, Houdini and Fusion integration - and I like such consistency!

[iLLiCiTiT]

Also pointing out that there is also _before_workfile_save and _after_workfile_save on IWorkfileHost so you can store the _about_to_save on the host itself too.

[BigRoy]

@sebastianbrandhuber I assume this is a change still to do?

[sebastianbrandhuber]

Yes, will implement this next week when back at work 👍

[BigRoy]

@moonyuet could you give this a thorough stress test? :)

[moonyuet]

The context change is successfully when switching folder and task. but failed to save the workfile.

Recording.2026-06-23.173638.mp4

Error log:

Traceback (most recent call last):
  File "<string>", line 9, in <module>
  File "C:\Users\Kayla\AppData\Local\Ynput\AYON\addons\core_1.9.6+dev-ayon-ui-qt-launcher\ayon_core\pipeline\create\context.py", line 287, in __init__
    self.reset(discover_publish_plugins)
  File "C:\Users\Kayla\AppData\Local\Ynput\AYON\addons\core_1.9.6+dev-ayon-ui-qt-launcher\ayon_core\pipeline\create\context.py", line 580, in reset
    self.reset_instances()
  File "C:\Users\Kayla\AppData\Local\Ynput\AYON\addons\core_1.9.6+dev-ayon-ui-qt-launcher\ayon_core\pipeline\create\context.py", line 1591, in reset_instances
    raise CreatorsCollectionFailed(failed_info)
ayon_core.pipeline.create.exceptions.CreatorsCollectionFailed: Failed to collect instances

[BigRoy]

Traceback (most recent call last):
  File "<string>", line 9, in <module>
  File "C:\Users\Kayla\AppData\Local\Ynput\AYON\addons\core_1.9.6+dev-ayon-ui-qt-launcher\ayon_core\pipeline\create\context.py", line 287, in __init__
    self.reset(discover_publish_plugins)
  File "C:\Users\Kayla\AppData\Local\Ynput\AYON\addons\core_1.9.6+dev-ayon-ui-qt-launcher\ayon_core\pipeline\create\context.py", line 580, in reset
    self.reset_instances()
  File "C:\Users\Kayla\AppData\Local\Ynput\AYON\addons\core_1.9.6+dev-ayon-ui-qt-launcher\ayon_core\pipeline\create\context.py", line 1591, in reset_instances
    raise CreatorsCollectionFailed(failed_info)
ayon_core.pipeline.create.exceptions.CreatorsCollectionFailed: Failed to collect instances

That sounds quite weird. Does the publisher UI refresh without errors before the save change? And does it still open publisher UI fine after?

It's weird it fails on collecting instances, but doesn't in stack trace tell us what it actually errors on.

[moonyuet]

Traceback (most recent call last):
  File "<string>", line 9, in <module>
  File "C:\Users\Kayla\AppData\Local\Ynput\AYON\addons\core_1.9.6+dev-ayon-ui-qt-launcher\ayon_core\pipeline\create\context.py", line 287, in __init__
    self.reset(discover_publish_plugins)
  File "C:\Users\Kayla\AppData\Local\Ynput\AYON\addons\core_1.9.6+dev-ayon-ui-qt-launcher\ayon_core\pipeline\create\context.py", line 580, in reset
    self.reset_instances()
  File "C:\Users\Kayla\AppData\Local\Ynput\AYON\addons\core_1.9.6+dev-ayon-ui-qt-launcher\ayon_core\pipeline\create\context.py", line 1591, in reset_instances
    raise CreatorsCollectionFailed(failed_info)
ayon_core.pipeline.create.exceptions.CreatorsCollectionFailed: Failed to collect instances

That sounds quite weird. Does the publisher UI refresh without errors before the save change? And does it still open publisher UI fine after?

It's weird it fails on collecting instances, but doesn't in stack trace tell us what it actually errors on.

It does have error from ayon-deadline-cloud, I will try to disabled that plugins and test if it is related.

[moonyuet]

Tested successfully in Nuke 16.0

[BigRoy]

All looks good - just pending the change requested here next week.