ID 458589 - C_Stitcher nodes created via Python do not evaluate until its control panel is opened

Problem summary
C_Stitcher nodes created via Python do not evaluate until its control panel is opened.

Customer reported version
Nuke 12.2v3

Customer reported platform
Windows 10

Steps to reproduce

1) Open Nuke and read in some images to stitch.

2) Navigate to Edit > Project Settings > Views and set up additional cameras for each Read node.

3) Create a C_CameraSolver node and connect its inputs to each of your Read nodes.

4) Click Match, then click Solve.

5) On the C_CameraSolver, select Cameras from the Export dropdown. Then click Create.

6) Create two JoinViews nodes - connect all of the Read nodes to one, and all of the Cameras to the other.

7) Create a C_CameraIngest node and connect its inputs to the appropriate JoinViews nodes. Your script should now look something like this:

​​

​

8) With the C_CameraIngest node selected in the Node Graph, run the following line of code in the ScriptEditor:

nuke.createNode("C_Stitcher2_1", inpanel = False)

Notice that the Viewer doesn't update. Creating a Write node and rendering the sequence will also render out images without evaluating the C_Stitcher node.

However, opening the control panel will cause the node to evaluate.

Expected behaviour
The C_Stitcher node should evaluate when added to a script via Python, without having to open the control panel.

Actual behaviour
C_Stitcher nodes created via Python do not evaluate until its control panel is opened.

Workaround
Opening and closing the node's control panel seems to make the node evaluate. You can open and close the control panel via Python with the following code:

node.showControlPanel()
node.hideControlPanel()

Reproduced by support
This bug has been reproduced in:
NukeX 12.2v3 - Windows 10 - Linux CentOS 7 - macOS 10.13 (High Sierra)
NukeX 12.0v1 - Windows 10
NukeX 11.0v1 (CaraVR 2.1v1) - Windows 10

Nuke 10.5v8 (CaraVR 2.1v3) - Windows 10 - Linux CentOS 7 - macOS 10.13 (High Sierra)

Earliest version tested
Nuke 10.5v8
- This issue appears to be in all versions of the product with the C_Stitcher2 node.