ID 594523 - DeepFromFrames does not seem to include the last frame of its frame range

Problem summary
DeepFromFrames does not seem to include the last frame of its frame range.
 
Customer reported version
Nuke 15.0v4
 
Customer reported platform
N/A
 
Steps to reproduce
 
1) Open Nuke.
 
2) Create 2 Constant nodes, one red and one green.
 
3) Create a Switch node that animates between inputs 0 and 1 on frames 1-2.
 
4) Connect the Constant nodes to the Switch node.
 
5) Add a DeepFromFrames node downstream of the Switch node.
 
6) Change the DeepFromFrames node's frame range knobs to 1 - 2.
 
7) Add a DeepSample node downstream of the DeepFromFrames. An example script is below:

Constant { inputs 0 color {0 0.2 0 0.9} name Constant2 selected true xpos -86 ypos -207}Constant { inputs 0 color {0.2 0 0 0.9} name Constant1 selected true xpos -441 ypos -213}Switch { inputs 2 which {{curve x1 0 1}} name Switch1 selected true xpos -261 ypos -49}DeepFromFrames { range_last 2 name DeepFromFrames1 selected true xpos -261 ypos 5}DeepSample { name DeepSample1 selected true xpos -261 ypos 49}

 
8) View the DeepSample node on frame 2. Notice that there are no rgba.green samples on this frame.
 
9) Update the DeepFromFrames node's frame range knobs to 1 - 3.
 
10) View the DeepSample node on frame 2.
NOTE: You will also see a visual difference in the Viewer when changing frames on this step.
 
Expected behaviour
The last frame of the DeepFromFrames node's frame range should be included in the frame range.
 
Actual behaviour
DeepFromFrames does not seem to include the last frame of its frame range.
In this example, this results in incorrect sample vales on the DeepSample node.
 
Workaround
Increase the DeepFromFrames node's frame range by 1.
 
Reproduced by support
This bug has been reproduced in:
Nuke 15.1v5 - Windows 10 - macOS 12
Nuke 12.0v1 - Windows 10 - macOS 12
 
Earliest version tested
Nuke 12.0v1 
- This issue appears to be in all tested versions of the product