ID 155623 - If a TCL comment on a node label only contains a node name then Nuke creates that node every time you change frame

Problem summary
Within most nodes under the 'Node' tab exists the 'label' field. This field is quite useful as it allows you to relay any text that is entered in this field on to the node itself in the Node Graph.

One advantage of the label field, is that you can also enter is commands and expressions to assist with passing through information from the script itself.

While this is useful, it has also been discovered that if a node is unintentionally called as a TCL command through using square brackets eg. Notes [Grade this node], what can occur is the creation of a node accidentally in the Node Graph.

In addition to the adverse effect of creating nodes sporadically within the script, if the label's text continues to be modified (or knobs changed) a crash will occur.

Customer reported version
nuke.12.2v2

Customer reported platform
centos7

Steps to reproduce
1) Create a Grade node

2) Within the Node tab, enter in the following text 'Notes [Grade this node]' into the label field
Result: This will create a new Grade node and an error stating that it could not find the 'this' knob

3) Attempt to add additional text or spaces to the label field
Result: Crash occurs after a few changes

Expected behaviour
While commands are expected to run correctly as TCL in a label field, it should not be possible to generate new nodes through a label field

Actual behaviour
When a TCL command that generates a node is entered into a label field of another node, a node is unexpectedly created in the Node Graph and can lead to a crash over time.

Workaround
Avoid using square brackets '[ ]' within the label field of a node, if the contents could generate a node. eg. [Add this], [Grade that]

If you do need to use square brackets, attempt to break the TCL association with a another character eg. [ - Add this], [ - Grade that], or use lower case [add this], [grade that]

Reproduced by support

This bug has been reproduced in:
Nuke 13.0v2 - Windows 7 - MacOS 10.15.6 - CentOS 7
Nuke 13.0v1 - Windows 7
Nuke 12.2v1 - Windows 7
Nuke 12.1v1 - Windows 7
Nuke 12.0v1 - Windows 7
Nuke 11.0v1 - Windows 7
Nuke 10.0v1 - Windows 7
Nuke 9.0v1 - Windows 7 - MacOS - CentOS 7

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