ID 562004 - Nuke crashes after Viewing a GeoDuplicate node and setting an invalid prim path

Problem summary:
Nuke crashes after Viewing a GeoDuplicate node and setting an invalid prim path 
 
Customer reported version:
Nuke 14.1v2
 
Customer reported platform:
N/A
 
Steps to reproduce:
1) Launch Nuke and create a GeoCube node in the Node Graph.
2) Create a GeoDuplicate node and View it.
3) In the GeoDuplicate's Properties, set the Prim Path knob to "test", or similar.
4) Observe Nuke's performance, and the following error messages printed to the Terminal:

 
Expected behavior:
The GeoDuplicate node should not cause Nuke to crash if an invalid string has been set as the prim path.
 
Actual behavior:
When Viewing a GeoDuplicate node, Nuke will crash if the Prim Path knob is set to an invalid string:

Error: Failed verification: ' i != _data.end() ' -- Tried to set field '.' on nonexistent spec at <primChildren>Error: Path <.> must be an absolute path to a prim, a prim variant-selection, or the pseudo-root.

 
Other malformed prim paths, like /a/b/, produce the following errors without crashing Nuke:

WARNING: GeoDuplicate1: Ill-formed SdfPath </a/b/>: syntax error ERROR: GeoDuplicate1: Cannot create prim at path '' because it is not a valid prim or prim variant selection path ERROR: GeoDuplicate1: Invalid empty path

 
Workaround:
No known workaround at this time.
 
Reproduced by Support in:
Nuke 15.0v2 - Windows 10, macOS 13 Ventura
Nuke 15.0v1 - Windows 10
Nuke 14.1v2 - Windows 10
Nuke 14.1v1 - Windows 10
 
Earliest version tested:
Nuke 14.1v1 - This feature (GeoDuplicate node) doesn't exist before this version