ID 135027 - Using an onCreate() callback for setInput() will connect with an Expression link rather than with an Input

Problem summary:
Using an onCreate() callback for setInput() will connect with an Expression link rather than with an Input.

Customer reported version:
nuke.11.2v3

Customer reported platform:
centos7

Steps to reproduce:

1) In Nuke, copy/paste the following code:

set cut_paste_input [stack 0]version 11.2 v3push $cut_paste_inputNoOp { name NoOp2 onCreate "n = nuke.thisNode()\nn.setInput(0,nuke.toNode('NoOp1'))" selected true xpos -323 ypos -156}NoOp { inputs 0 name NoOp1 selected true xpos -224 ypos -313}

2) Paste the above code a second time, observing placement of the NoOp nodes and the Input.

3) Observe that an Expression is linked rather than the Input itself.

Expected behavior:
The Input should be linked to the NoOp1 node instead of an Expression.

Actual behavior:
An Expression link is created from the onCreate callback for any subsequent NoOp2 node pasted in.

Workaround:
There is no workaround available at this time.

Reproduced by Support in:
Nuke 11.3v1 - Windows 10, CentOS 7, macOS 10.13.6 High Sierra

Nuke 11.2v1 - Windows 10

Nuke 11.1v1 - Windows 10

Nuke 11.0v4 - Windows 10, CentOS 7, macOS 10.13.6 High Sierra - regression

Unable to reproduce bug in:
11.0v3 - Windows 10, CentOS 7, macOS 10.13.6 High Sierra

Earliest version tested:
Nuke 11.0v3 - This issue no longer appears in this version and has regressed

in Nuke 11.0v3 and below, there is a flash of an expression linked to the NoOp node, however, it is not visible on screen after creation.