ID 514396 - Adding certain nodes to the STMap input breaks the output, making it repeat the bottom left pixel over the whole image

Follow

Problem summary:
Adding certain nodes to the STMap input breaks the output, making it repeat the bottom left pixel over the whole image.
This happens when at least any of the following nodes are upstream of the STMap node:

add32p
AppendClip
Assert
C_GenerateMap2_1
Colorspace
Copy
CopyBBox
CopyRectangle
Dissolve
Encryptomatte
Expression
FrameRangeGamma
Keymix
Multiply
OCIOCDLTransform
OCIOColorSpace
remove32p
Retime
TimeDissolve
TimeWarp
VectorToMotion

Customer reported version:
Nuke 13.2v2

Customer reported platform:
CentOS 7

Steps to reproduce:
1) Open Nuke and open attached script
2) Connect one of the Breaking Nodes above the STMap node, it will now render the bottom left color of the image:

*Sometimes you may need to switch the Switch node input to force an upstream refresh

Expected behavior:
The STMap node should be rendered correctly, regardless of the nodes upstream.

Actual behavior:
Having certain nodes upstream causes the STMap to render the bottom left pixel everywhere.

Workaround:
Between the STMap and the upstream node, create a Grade, Merge or Transform node. Additionally, changing the STMap node's filter knob to impulse seems to resolve the issue, but this method does disable filtering as stated in the tooltip:


Reproduced by Support in:
Nuke 13.2v4 - Windows 10 - macOS 12.4 - CentOS 7
Nuke 13.1v1 - Windows 10 - macOS 12.4 - CentOS 7 - Regression

Unable to reproduce bug in:
Nuke 13.0v9 - Windows 10 - macOS 12.4 - CentOS 7

Earliest version tested:
Nuke 13.0v9 - This issue doesn't appear in this version and has regressed

    We're sorry to hear that

    Please tell us why