ID 539790 - Inconsistent behaviour between Write nodes which have "read file" enabled and disabled, depending on whether when they are executed from inside or outside a Group

Follow

Problem summary
Inconsistent behaviour between Write nodes which have "read file" enabled and disabled, depending on whether when they are executed from inside or outside a Group.
 
Customer reported version
Nuke 13.2v6
 
Customer reported platform
CentOS 7
 
Steps to reproduce
 
1) Open Nuke.
 
2) Create a CheckerBoard.
 
3) Create Write node downstream of the CheckerBoard. 
 
4) Set the Write node's file knob to render a file to a valid location.
 
5) Select the Write node, then press F7 to render some frames.
RESULT: The Write node is rendered successfully.
 
6) On the Write node, enable read file.
 
7) Select the Write node again, and render it again by pressing F7.
RESULT: The Write node is rendered successfully.
 
8) Disable read file on the Write node.
 
9) Add the Write node to a Group by selecting it and pressing Ctrl+G.
 
10) Select the Group node and press F7 to render the Write node.
RESULT: The Write node is rendered successfully.
 
11) Open the Group (shortcut: Ctrl+Enter).
 
12) On the Write node, enable read file.
 
13) Return to the top level of the Node Graph, select the Group node, and press F7.
RESULT: The Write node is not rendered and the following error is returned:
 


 
Expected behaviour
The behaviour of Write nodes that have read file enabled should be consistent with those that have read file disabled, and still consistent regardless of whether they are inside or outside a Group. 
 
Actual behaviour
Inconsistent behaviour between Write nodes which have "read file" enabled and disabled, depending on whether when they are executed from inside or outside a Group.
 
Workaround
Unknown. 
 
Reproduced by support
This bug has been reproduced in:
Nuke 14.0v4 - Windows 10 - Linux CentOS 7
Nuke 10.0v1 - Windows 10 - Linux CentOS 7 
 
Earliest version tested
Nuke 10.0v1
- This issue appears to be in all tested versions of the product
 

    We're sorry to hear that

    Please tell us why