Provide a way to distinguish between terminating error vs. non-terminating error #3158

Activity

1. Hemant Mahawar (HemantMahawar)

   self-assigned this

   on Feb 16, 2017
2. apetitjean commented on Feb 23, 2017

   

   Arnaud Petitjean (apetitjean)

   on Feb 23, 2017

   More actions

   That is definitely something that should be addressed! That makes just 10 years we struggle with that ;-)

   👍React with 👍1Reacted by Michael Klement
3. mklement0 commented on Jul 19, 2017

   

   Michael Klement (mklement0)

   on Jul 19, 2017

   Last edited by mklement0

   Contributor

   More actions

   Related: #4292

   Given the current capabilities:

   • In hindsight, by inspecting $Error, I don't think there's a (straightforward) way to classify previous errors - though I'm not sure that's needed. [Update: It is needed in order to provide error type-specific coloring, for instance - see Suggestion: Add an $ErrorView option that displays concise, single-line error information and consider making that the default - default formatting of ErrorRecord #3647]

   • To distinguish errors as they occur, use a Try / Catch statement: only terminating errors will trigger the Catch handler:

   Note: I'm using 1 / 0 as a stand-in for a pipeline-terminating error here:

   # Trigger a pipeline-terminating error; works the same with a script-terminating error (Throw).
   $errCountBefore = $Error.Count
   $terminatingErrorOccurred = $False
   Try {
     1 / 0
   }  Catch { # TRIGGERED by a TERMINATING ERROR - both pipeline-terminating and script-terminating
     # Note: To also *output* the error, use Write-Error $_, but note that this
     #       *duplicates* the automatically generated $Error entry.
     Write-Error $_
     $terminatingErrorOccurred = $True
   }
   if ($terminatingErrorOccurred)            { 'Terminating error occurred.' }
   elseif ($Error.Count -gt $errCountBefore) { 'Non-terminating error occurred.' }
   
   '---'
   
   # Trigger a non-terminating error.
   $errCountBefore = $Error.Count
   $terminatingErrorOccurred = $False
   Try {
     # A non-terminating error prints its output to the error stream,
     # irrespective of any enclosing Try/Catch handler.
     Get-Item /NoSuch
   }  Catch {  # NOT triggered by a NON-TERMINATING ERROR
    $terminatingErrorOccurred = $True
   }
   if ($terminatingErrorOccurred)            { 'Terminating error occurred.' }
   elseif ($Error.Count -gt $errCountBefore) { 'Non-terminating error occurred.' }

   The above yields:

   /Users/jdoe/Desktop/pg/pg1.ps1 : Attempted to divide by zero.
   ....
   Terminating error occurred.
   ---
   Get-Item : Cannot find path '/NoSuch' because it does not exist.
   ...
   Non-terminating error occurred.
   
4. joeyaiello commented on Mar 13, 2019

   

   Joey Aiello (joeyaiello)

   on Mar 13, 2019

   Contributor

   More actions

   Steve Lee (@SteveL-MSFT): I want this for Functions per our discussion on critical vs error logs.

   /cc TylerLeonhardt Dongbo Wang (@daxian-dbw)

   👀React with 👀1Reacted by Rain Sallow (/u/ta11ow)
5. Steve Lee (SteveL-MSFT)

   added

   Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bug

   WG-Enginecore PowerShell engine, interpreter, and runtimecore PowerShell engine, interpreter, and runtime

   on Mar 15, 2019
6. Steve Lee (SteveL-MSFT)

   added this to the 6.3-Consider milestone on Mar 15, 2019
7. Steve Lee (SteveL-MSFT)

   added

   Resolution-DuplicateThe issue is a duplicate.The issue is a duplicate.

   on Mar 15, 2019
8. SteveL-MSFT commented on Mar 15, 2019

   

   Steve Lee (SteveL-MSFT)

   on Mar 15, 2019

   Last edited by SteveL-MSFT

   Member

   More actions

   Dupe of #4781. Yes, this one is older, but the latter has more discussion.
9. Steve Lee (SteveL-MSFT)

   closed this as completedon Mar 15, 2019