ID 550120 - Classic 3D System snap_menu options produce a "NoneType object is not subscriptable" error if a disabled ReadGeo node is present

Follow

Problem summary:
Classic 3D System snap_menu options produce a "NoneType object is not subscriptable" error if a disabled ReadGeo node is present

 
Customer reported version:
Nuke 14.0v2
 
Customer reported platform:
Windows 10
 
Steps to reproduce:
1) Launch Nuke and create a ReadGeo node in the Node Graph.
2) In the ReadGeo's Properties panel, use the file browser to select any valid geometry file.
3) With the ReadGeo node selected, press "D" to Disable it.
4) Create a Card node and View it.
5) In the Viewer, switch to Vertex selection mode and select some vertices on the Card.
6) In the Card's Properties panel, choose any option from the snap_menu:

7) Observe the 'NoneType' object is not subscriptable error message:

 
Expected behavior:
The snap_menu options should not produce errors, regardless of any disabled ReadGeo nodes in a Nuke script.
 
Actual behavior:
A "NoneType" exception is raised when attempting to use the snap_menu if a disabled ReadGeo node is present in the script.
 
The same issue also occurs while trying to access the snap_menu functionality via Python:
from nukescripts import snap3dsnap3d.getSelection()
 
Workaround:
Besides enabling any disabled ReadGeo nodes, there is no known workaround at this time.
 
Reproduced by Support in:
Nuke 14.0v5 - Windows 10, CentOS 7
Nuke 14.0v1 - Windows 10, CentOS 7 - Regression
 
Unable to reproduce bug in:
Nuke 13.2v8 - Windows 10, CentOS 7
 
Earliest version tested:
Nuke 13.2v8 - This issue doesn't appear in this version and has regressed 

    We're sorry to hear that

    Please tell us why