ID 158473 - Spherical Transform showing seams on Output Type (ie Sphere, Mirror Ball, lat long)

Problem summary
Using SphericalTransform nodes to create an 'Angular map 180' texture from five Cube inputs results in black seams.

Customer reported version
Nuke 11.3v3

Customer reported platform
CentOS 7

Steps to reproduce

1) Open the attached script.

- The script contains a Constant node that is connected to five different SphericalTransform nodes.

- All SphericalTransform nodes have their Input Type set to 'Cube' and Output Type set to 'Angular map 180'.

- The first SphericalTransform has no rotation applied.

- The second and third SphericalTransform nodes have rotation applied about the Y-axis (90 and -90 respectively).

- The fourth and fifth SphericalTransform nodes have rotation applied about the X-axis (90 and -90 respectively).

- The SphericalTransform nodes are all then Merged together 

2) View the result and notice that there are black seams in the Viewer

Expected behavior
This should create a seamless image in the Viewer.

Actual behavior
There are black seams on the image.

Workaround
Add the AdjBBox node and add 1 pixel.

Reproduced by Support in:

Nuke 13.0v4 - Windows 10

Nuke 13.0v1 - Windows 10

Nuke 12.0v1 - Windows 10

Nuke 11.3v3 - WIndows 10 - Linux CentOS 6 - macOS 10.13 (High Sierra)

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.0v1 - Windows 10 - Linux CentOS 6 - macOS 10.13 (High Sierra)

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