nuke
nuke copied to clipboard
Fixed invalid check for current LogLevel in ProcessException message.
Logger was deprecated some time ago, and it seems that the Logger.LogLevel property is always LogLevel.Normal now.
This broke the formatting of exception messages for ProcessException so that they no longer included the tool output if verbosity was set to Verbose (or Trace). The correct place to check current log level seems to be Logging.Level. Updated the message formatting in ProcessException to fix this.
I confirm that the pull-request:
- [x] Follows the contribution guidelines
- [x] Is based on my own work
- [x] Is in compliance with my employer