ID 598753 - Exporting from a comp container, where the temp .nk name matches your comp, will result in your original .nk file being overwritten/deleted

Problem summary
Exporting from a comp container, where the temp .nk name matches your comp, will result in your original .nk file being overwritten/deleted
 
Customer reported version
Nuke 16.0v1
 
Customer reported platform
Windows 11
 
Steps to reproduce
 
1) Open Nuke Studio.
 
2) In the Node Graph, create a simple comp and save it. This script can just be a CheckerBoard and a Write node.
 
3) Import this script into the Project Bin (File > Import File(s)...) and drop it on to the timeline.
 
4) Right click the track item > Render Comp. This is required before exporting from the comp again.
 
5) Right click the track item > Export.
 
6) Create an export preset, like so:
 

 
In this case, my original comp is saved as C:/temp/163746/myscript.nk and the preset will export the frames to the same directory.
 
7) Press Export.
 
8) Once the render has finished, your comp container will be offline in the timeline. This is because the temporary .nk script had the same name as your original .nk file, and it has now been deleted.
 
Expected behaviour
Nuke Studio should warn the user about naming collisions, or just name the temporary export .nk script to something else.
 
Actual behaviour
The temporary .nk script has the same name as the original comp, so Nuke Studio just overwrites and deletes it.
 
Workaround
Unknown.
 
Reproduced by support
This bug has been reproduced in:
Nuke 16.0v1 - Windows 11 - macOS 12
Nuke 12.0v1 - Windows 11 - macOS 12
 
Earliest version tested
Nuke 12.0v1
- This issue appears to be in all tested versions of the product