ID 163119 - node.hasError() not detecting errors with incomplete EXRs when run in a loop

Problem summary
node.hasError() and node.treeHasError() are not detecting errors with incomplete EXRs when run in a loop

Customer reported version
Nuke 11.3v3

Customer reported platform
fedora

Steps to reproduce

1) Open Nuke and Read in an EXR sequence that contains at least one corrupted frame.

2) Run the following code in the Script Editor:


the_node = nuke.toNode('Read1')firstFrame = 340 #change as applicable lastFrame = 345 #change as applicable for frames in range(firstFrame,lastFrame):    nuke.frame(frames)    print str(nuke.frame())+"="+str(the_node.hasError())

This code loops each frame and should return True or False for each frame.
This works as expected on missing frames, but does not detect errors with incomplete EXRs.

Expected behaviour
The erroring frames should should return True when node.hasError() is run in a loop.

Actual behaviour
The erroring frames always returns False when node.hasError() is run in a loop.

Reproduced by support
This bug has been reproduced in:
Nuke 11.3v4 - Windows 10 - macOS 10.13 High Sierra - Linux CentOS 7
Nuke 11.3v1 - Windows 10
Nuke 11.2v1 - Windows 10
Nuke 11.1v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.5v1 - Windows 10
Nuke 10.0v1 - Windows 10
Nuke 9.0v1 - Windows 10
Nuke 8.0v7 - Windows 10 - macOS 10.13 High Sierra - Linux CentOS 6

Earliest version tested
Nuke 8.0v7
- This issue appears to be in all versions of the product

We're sorry to hear that

Please tell us why