ID 392704 - Using node.dependent() doesn't return dependencies within an onDestroy callback

Problem summary
Using the node.dependent() function doesn't work with an onDestroy callback for Linux and Mac.

This issue appears to be a regression with Nuke11.0v3.

Customer reported version
nuke.11.2v3

Customer reported platform
centos7

Steps to reproduce

1) Run this in the script editor:

def onDeleteDependencyTest():    sourceNode = nuke.thisNode()    print sourceNode.dependent()    for targetNode in sourceNode.dependent():        print targetNode.name()onDeleteDependencyTest()

2) Paste this into the node graph:

Grade { blackpoint {{Grade1.blackpoint}} name Grade2 selected true xpos -13 ypos -244}Transform { inputs 0 rotate {{Grade1.blackpoint}} center {1024 778} name Transform1 selected true xpos 95 ypos -153}ColorCorrect { inputs 0 saturation {{Grade1.blackpoint}} name ColorCorrect1 selected true xpos 258 ypos -195}Grade { inputs 0 blackpoint 0.06 name Grade1 onDestroy HelloWorld() selected true xpos 170 ypos -319}

3) Delete Grade1

Expected Result:

​

Actual behaviour
Linux and Mac return [] , as it could not find the dependent locations.
Windows displays the expected behaviour.

Workaround
Unknown. 

Reproduced by support

This bug has been reproduced in:
Nuke11.3v4 - Mac10.14 - CentOS7
Nuke11.3v1 - Mac10.14 - CentOS7
Nuke11.2v1 - Mac10.14 - CentOS7
Nuke11.1v1 - Mac10.14 - CentOS7
Nuke11.0v4 - Mac10.14 - CentOS7 - regression

Unable to reproduce bug in:
Nuke11.3v4 - Windows 7
Nuke11.0v3 - Mac10.14 - CentOS7


Earliest version tested
- This issue no longer appears in this version and has regressed