ID 466858 - A boost::filesystem::status Access is denied message is given when specific errors occur.

Problem summary:
A boost::filesystem::status message is given when specific errors occur.

This message prompt can occur for different errors such as "Access is denied". The below steps to reproduce are an example to trigger the prompt with Permissions denied.

Customer reported version:

nuke.11.2v5

Customer reported platform:
centos7

Steps to reproduce:

1) From Nuke, open the Preferences... menu. (Edit > Preferences... or Shift+S)

2) Select Localization and ensure it's enabled, also setting an auto-localize path for a networked location.

3) Add a Read node with a networked file from the auto-localized path.

4) View the Read node by pressing 1 on the keyboard to set the Viewer node.

5) Save and close the script.

6) Access the ingested Read file from the networked location and set permissions equivalent to 700 in Linux.

7) Launch Nuke and open the script observing any errors.

Expected behavior:
A user-friendly error message should appear, rather than boost::filesystem::status errors.

Actual behavior:
A "boost::filesystem::status error: Access is denied:"  messages are prompted when taking specific actions in a script.

Workaround:
No current workaround is available at this time.

Reproduced by Support in:
Nuke 11.3v4 - Windows 10, CentOS 7

Nuke 11.3v1 - Windows 10

Nuke 11.2v1 - Windows 10

Nuke 11.1v1 - Windows 10, CentOS 7 - regression

Unable to reproduce bug in:
11.0v4 - Windows 10, CentOS 7
 

Earliest version tested:
Nuke 11.0v4 - This issue no longer appears in this version and has regressed