ID 331214 - Exported Read nodes from Nuke Studio don't inherit "on_error" knob values from Timeline Read nodes

Problem summary
The "on_error" Read node knob value is not carried over when the Read node is exported as a Nuke script from Nuke Studio to Nuke. 

Customer reported version
nuke.11.1v1

Customer reported platform
centos7

Steps to reproduce

1) Launch NukeStudio 11.1v1 and import an image sequence (ctrl+ i).

2) Drag and drop this image sequence from the Bin onto the Timeline. 

3) Double click the footage on the Timeline and note that the Read node knob value the "on_error" knob defaults to "error".

4) With the footage selected, right click it on the Timeline and select "Create Comp" from the "Effects" drop-down menu and set your directory to wherever you would like, eg, Desktop, and select "Open"

5) This will generate a Nuke comp titled "VFX 1" on the Timeline above your footage. Double click it to open up the script inside of the Nuke Node Graph in Studio.

6) Note the results of the "on_error" knob values of the newly created Read node within the comp. The "on_error" knob value is now set to "black" instead of "error" from the Timeline Read node from Studio.   

Workaround
Two options: 

1) Manually set the Read node knob value within the Nuke scripts  "on_error" knob value from "black" to "error" within the Nuke scripts Read node.

---

2.1) Using the  Knowledge Base article: Q100195: How to customise Nuke script exports from NukeStudio/Hiero as a guide, download the attached "customiseExports.py" script I have attached to this report, it has been slightly modified to only change the "on_error" Read node knob value to "black".

2.2) Place the script inside of your /Python/Startup directories within your .nuke folder, should they not exist, they can manually be created.
/.nuke/Python/Startup/customiseExports.py

For more information please see Q100048: Nuke Directory Locations for locating your .nuke directory on your preferred OS.

As stated in the file, 

 def onNodeAdded(self, node):
""" Callback when a node is added. Return the node that should actually be added. """
 if node.type() == "Read": # Change for the type of node you want to edit
 # Make adjustments to all nodes of that type
      node.setKnob("on_error", "black") # This sets each Read nodes missing frames to black

If the node is a "Read" node set the "on_error" knob value to "black" when exported. This will correct the Export behavior when exporting a Read node from Nuke Studio to non-Studio Nuke. Please note that when you implement this change this will set the "on_error" knob value always to "black", should you wish to change it to something else, you can either remove the python script or edit the knob value within the Nuke script to meet your needs.  


Reproduced by support
This bug has been reproduced in:
NukeStudio 11.1v1  - CentOS 7.4 - Windows 10 - MacOSX 10.13 [Regression]


Earliest version tested
NukeStudio 11.1v1  - CentOS 7.4 - Windows 10 - MacOSX 10.13 - Feature not present in earlier releases.

Expected behaviour
The "on_error" Read Node knob value would carry over from the Nuke Studio exported Read node into Nuke. 

Actual behaviour
The "on_error" knob value does not carry over the same Read knob values that were set within Nuke Studio to the exported Nuke script.